CVE-2026-43111: HID: roccat: fix use-after-free in roccat_report_event
In the Linux kernel, the following vulnerability has been resolved:
HID: roccat: fix use-after-free in roccat_report_event
roccat_report_event() iterates over the device->readers list without
holding the readers_lock. This allows a concurrent roccat_release() to
remove and free a reader while it's still being accessed, leading to a
use-after-free.
Protect the readers list traversal with the readers_lock mutex.
Security readout for executives and security teams
Plain-English summary
A flaw in the Linux ROCCAT HID driver can let a local, low-privileged user trigger access to freed kernel memory during concurrent device-reader activity. Successful exploitation could compromise confidentiality, integrity, or availability. The issue is not remotely exploitable under the supplied CVSS vector.
Executive priority
Prioritize remediation on shared workstations, multi-user systems, and other hosts permitting untrusted local access. Treat this as a high-priority kernel update, but not an internet-edge emergency based on the local attack vector and absent exploitation evidence.
Technical view
roccat_report_event() traverses device->readers without holding readers_lock. A concurrent roccat_release() can remove and free a reader still being accessed, causing a kernel use-after-free. The stable fixes protect list traversal with the existing mutex.
Likely exposure
Exposure is concentrated on affected Linux kernels where the ROCCAT HID driver path is present and usable. Exploitation requires local access with low privileges; network-only attackers are not directly exposed. The supplied version list is ambiguous, so verify distribution-specific kernel builds against the cited fixes.
Exploitation context
The bundle does not establish active exploitation, and CVE-2026-43111 is not identified as a KEV entry. The CVSS 3.1 score is 7.8 because a local, low-privileged attacker could potentially affect kernel confidentiality, integrity, and availability without user interaction.
Researcher notes
The core condition is a race between unlocked readers-list traversal and release-time removal and freeing. The supplied record names no CWE and provides no exploitability proof. Version data includes repeated commit identifiers and unclear boundaries; branch-level exposure should therefore be established from vendor advisories or backport records.
Mitigation direction
Apply the distribution kernel update containing the relevant cited stable fix.
Reboot affected systems into the corrected kernel after installation.
Until patched, limit untrusted local access on systems using the ROCCAT HID driver.
Consult Linux distribution guidance when package versions do not map clearly to upstream commits.
Validation and detection
Inventory running kernel builds and identify systems where the ROCCAT HID driver is present or used.
Compare distribution package changelogs or source against the cited fix commit for each kernel branch.
After remediation, confirm the corrected kernel is running, not merely installed.
Reassess local account exposure on any system awaiting an update.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-43111 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
9Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.