CVE-2026-93188 — HID: roccat: bound device-supplied profile index
In the Linux kernel, the following vulnerability has been resolved: HID: roccat: bound device-supplied profile index kone_keep_values_up_to_date() and kone_profile_activated() use an 8-bit, device-supplied profile value as an index into the 5-element kone->profiles[] array without a range check. A malicious USB device claiming the Roccat Kone id can send a switch-profile event (or a startup_profile read at probe) with an out-of-range value and make the driver read out of bounds; the result is exposed via the actual_dpi sysfs attribute. Reject out-of-range indices in both paths. This was found with static analysis and confirmed with the KUnit test added in the following patch (KASAN: slab-out-of-bounds).
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 14bf62cde79423a02a590e02664ed29a36facec1 and < 686e5c3bd378933b4e795fcc7d40c5aad358eaaa≥ 14bf62cde79423a02a590e02664ed29a36facec1 and < 0a139188a7ce4baab7acc5d60e0d1c8657f9b4d4≥ 14bf62cde79423a02a590e02664ed29a36facec1 and < 67d7851f113fd0205dd27416d3c47ab32b176097≥ 14bf62cde79423a02a590e02664ed29a36facec1 and < 4b29be4b23bc28f59def1485702887e395256e11≥ 14bf62cde79423a02a590e02664ed29a36facec1 and < 579c78c8c317ecff8b6b820c227c93e6ec4e565d≥ 14bf62cde79423a02a590e02664ed29a36facec1 and < 635914c60da26a9892f27ffb5edcc922a10effab≥ 14bf62cde79423a02a590e02664ed29a36facec1 and < 99330b12376c3373ab555c24bc797630f03b81a2≥ 14bf62cde79423a02a590e02664ed29a36facec1 and < 43fae42628a8c10fa8981773d7ec9f1a367821a7 and 1 moreversion 2.6.35 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/686e5c3bd378933b4e795fcc7d40c5aad358eaaa
- git.kernel.org/stable/c/0a139188a7ce4baab7acc5d60e0d1c8657f9b4d4
- git.kernel.org/stable/c/4b29be4b23bc28f59def1485702887e395256e11
- git.kernel.org/stable/c/635914c60da26a9892f27ffb5edcc922a10effab
- git.kernel.org/stable/c/99330b12376c3373ab555c24bc797630f03b81a2
- git.kernel.org/stable/c/43fae42628a8c10fa8981773d7ec9f1a367821a7
- git.kernel.org/stable/c/67d7851f113fd0205dd27416d3c47ab32b176097
- git.kernel.org/stable/c/579c78c8c317ecff8b6b820c227c93e6ec4e565d
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 1d
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 1d
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 2d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 2d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 2d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-93188 is "HID: roccat: bound device-supplied profile index", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.20% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.