# CVE-2026-93188: HID: roccat: bound device-supplied profile index

> A malicious USB device can trigger an out-of-bounds read in the Linux kernel Roccat driver, exposing memory contents via sysfs.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102762, BELL-CVE-2026-93188, DEBIAN-CVE-2026-93188, GHSA-vx3m-3j77-8829, UBUNTU-CVE-2026-93188

## What is CVE-2026-93188?

CVE-2026-93188 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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).

## Which versions are affected by CVE-2026-93188?


## How do I fix CVE-2026-93188?

Apply the vendor's patch.

## Is CVE-2026-93188 being exploited?

There is no known exploitation of CVE-2026-93188 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93188 and fix it if it is affected.

What it is: CVE-2026-93188 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-93188 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93188/ (Markdown: https://insights.sbomify.com/CVE-2026-93188/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93188
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93188
- OSV: https://osv.dev/vulnerability/CVE-2026-93188

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93188/
Summaries are generated and may contain mistakes; the official description above is the record.