# CVE-2026-89627: HID: roccat: free buffered reports when destroying device

> A memory leak in the Linux kernel's Roccat HID driver allows local attackers to exhaust system memory by repeatedly connecting and disconnecting devices.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-100359, BELL-CVE-2026-89627, DEBIAN-CVE-2026-89627, GHSA-v9hj-cvcm-4mj3, UBUNTU-CVE-2026-89627

## What is CVE-2026-89627?

CVE-2026-89627 is a memory corruption vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

HID: roccat: free buffered reports when destroying device

roccat_report_event() duplicates each report with kmemdup() and stores
the allocation in a circular-buffer slot. The allocation is released only
when that slot is reused.

The device destruction paths free struct roccat_device without releasing
reports still stored in cbuf[]. This makes those allocations unreachable
and leaks up to ROCCAT_CBUF_SIZE report buffers per device.

Add a small destructor that frees every buffered report before freeing the
device, and use it in both paths that can destroy a registered device.

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


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

Apply the vendor's patch.

## Is CVE-2026-89627 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89627 is a memory corruption vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-89627 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-89627/ (Markdown: https://insights.sbomify.com/CVE-2026-89627/index.md)
```

## Sources

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

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