[CVE-2026-93188][MODERATE REGULAR] HID: roccat: bound device-supplied profile index [ Upstream

[CVE-2026-93188][MODERATE REGULAR] HID: roccat: bound device-supplied profile index [ Upstream

[AL-KERNEL]

CVE: CVE-2026-93188
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: HID: roccat: bound device-supplied profile index [ Upstream
Commit: 686e5c3bd378933b4e795fcc7d40c5aad358eaaa
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=686e5c3bd378933b4e795fcc7d40c5aad358eaaa
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93188
Analysis date: Thu, 17 Sep 2026 23:22:50 -0400
ActionableScore: 3
ActionableScore lower bound: unknown
Actionable bucket: Borderline / manual review recommended
Manual review required: YES

Summary:
No one-sentence report phrase was found.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-93188 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93188

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: MODERATE REGULAR
Manual review required: YES

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-93188	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-93188 CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L';CWE-125;CWE-129;*CWE-20;Other CVSS 'AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N';BEST CVSS score: '3.5';DESCR 'A malicious USB HID device claiming the Roccat Kone id can provide an out-of-range profile index that is used to read outside the 5 element profile array. The out-of-bounds value can be reached during profile activation at probe time or through a switch profile event, and the resulting value may be exposed through the actual_dpi sysfs attribute. For the CVSS the PR:N is used because the attacker does not need an account on the victim system if they can attach or cause attachment of the malicious USB device. The issue is not network reachable and requires physical device presence or user assisted device attachment. Impact is mainly limited confidentiality exposure from an out-of-bounds read. Availability impact is only included in the paranoid score because KASAN confirms a slab out-of-bounds condition and hardened or debug kernels may turn this into a crash.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline / manual review recommended (with actual score 3)  SKIP CVE-2026-93188 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: url YES  NO NO unknown 	MAYBE	KASAN OOB USB SIMPLEFIX HARDWARE LINUS TEST  DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_GUESSCVSS INCREASED_FROM_LOW_BASED_ON_REQUIREMANUALCHECK DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4	-	-	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=3
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=NO
NamespaceScopedPrivilege=NO
ImportantCandidate=NO
ManualReview=RECOMMENDED
AutoDowngradeAllowed=YES

1. ActionableScore

* Raw conservative score: 3
* Conservative score: 3
* Raw paranoid score: 3
* Paranoid score: 3
* Final recommended bucket: **Borderline / manual review recommended**::

No floor or cap changed the score.

2. Signal breakdown

Positive signals:

* +1 Weak / indirect memory safety primitive. The device supplied profile value is used as an unchecked index into a 5 element `kone->profiles[]` array, producing an out of bounds read.
* +1 Confidentiality plausible. The out of bounds read result can affect `actual_dpi`, which is exposed through the `actual_dpi` sysfs attribute.
* +1 Firmware / device mediated external influence. The attacker controlled value comes from a malicious USB HID device claiming the Roccat Kone id.

Non awarded signals:

* RealUAF not awarded. No freed object or stale lifetime use is established.
* Strong corruption not awarded. The patch supports read outside the array, not OOB write, arbitrary write, controlled reclaim, or callback control.
* Reliable kernel crash not awarded. KASAN confirms slab out of bounds in testing, but the supplied evidence mainly establishes OOB read and limited disclosure, not a production reliable crash.
* Remote reachability not awarded. The issue requires physical or user assisted USB device attachment, not network traffic.
* LPE not awarded. No privilege escalation primitive is established.
* ImportantCandidate not set. The primitive is limited OOB read with low bandwidth sysfs exposure and no stronger corruption evidence.

3. Reachability analysis

The attacker is a malicious USB HID device or an actor who can cause such a device to be attached to the victim system. No host account or host administrator privilege is required once the device is attached, so HostAdminRequired is NO. NamespaceScopedPrivilege is NO because the path is a physical HID device driver path, not a namespace scoped capability path.

The complete trigger requires the vulnerable Roccat Kone driver to bind to a device claiming the expected id. The attacker controls the 8 bit profile value delivered either during probe via startup profile state or later via a switch profile event. There is no network reachability and no local namespace based trigger. No race or special timing is needed.

4. Primitive and severity interpretation

The exact primitive is a device controlled out of bounds read from `kone->profiles[]`. This is not active structured UAF and not fixed stale storage. It is an unchecked index bug with a plausible low value disclosure path through sysfs.

The demonstrated consequence is limited information exposure via `actual_dpi`. A crash is possible in debug or hardened environments, but a reliable host wide production crash is not established. There is no evidence of write corruption, object lifetime corruption, refcount corruption, security boundary bypass, or privilege escalation.

PrimitiveClass is CLASS_C because the established behavior is a weak memory safety issue with limited disclosure and no independently useful corruption primitive. ImportantCandidate is NO because there is no strong exploitation leverage beyond the bounded OOB read. AutoDowngradeAllowed is YES because the issue appears suitable for low priority handling after manual confirmation, rather than Important class escalation.

5. One-sentence report phrase

A malicious USB HID device claiming the Roccat Kone id can provide an out of range profile index that causes an out of bounds read from the profile array, with the resulting value potentially exposed through the actual_dpi sysfs attribute.

6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Reason: this is a real memory safety issue with a user visible disclosure path, but the evidence supports only limited OOB read impact and does not establish UAF, OOB write, LPE, or reliable host crash.

7. Call-site confidence

Call-site confidence: high

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: HID: roccat: bound device-supplied profile index [ Upstream
Commit: 686e5c3bd378933b4e795fcc7d40c5aad358eaaa
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=686e5c3bd378933b4e795fcc7d40c5aad358eaaa

Changed files:
  drivers/hid/hid-roccat-kone.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=686e5c3bd378933b4e795fcc7d40c5aad358eaaa

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-93188 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-93188

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
  The Best / paranoid CVSS vector: AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
  The Best / paranoid CVSS score: 3.5

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: unknown
  Paranoid ActionableScore: 3

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: MODERATE
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): MODERATE REGULAR

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).