Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 38 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 206f5f2fcb5ff5bb0c60f9e9189937f3ca03e378 – < cebb20b9a29cfc90bf56e54337333084f85a69dd
    • affected 206f5f2fcb5ff5bb0c60f9e9189937f3ca03e378 – < 690da9177e64bcfda2f4c0b5b8465178e4a236d8
    • affected 206f5f2fcb5ff5bb0c60f9e9189937f3ca03e378 – < b3cc411daa50b39ba5706492a80a5a0804d9c85f
    • affected 206f5f2fcb5ff5bb0c60f9e9189937f3ca03e378 – < 4cb3ff31d237ad1f515455c497ef07d7172d912b
    • affected 206f5f2fcb5ff5bb0c60f9e9189937f3ca03e378 – < 943b8dc2c6044c01e36395f51bb809a4b6bdfd22
    • affected 206f5f2fcb5ff5bb0c60f9e9189937f3ca03e378 – < da00eac19feef209c9591e48c860afc2014603be
    • affected 206f5f2fcb5ff5bb0c60f9e9189937f3ca03e378 – < fbb5a60f5c31b5625f0d89a79912fbcb2559289b
    • affected 206f5f2fcb5ff5bb0c60f9e9189937f3ca03e378 – < bbff0ccbff360a5498075525005f6a913239a3d7
  • Linux · Linux

    • affected 2.6.35
    • unaffected < 2.6.35
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89627 badge
[![CVE-2026-89627](https://cveledger.app/badge/CVE-2026-89627.svg)](https://cveledger.app/cve/CVE-2026-89627)

Record last updated .