Use-After-Free in Linux Kernel HID Roccat Driver

Publication date: 2026-05-06

Last updated on: 2026-06-01

Assigner: kernel.org

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-05-06

Last Modified

2026-06-01

Generated

2026-07-06

AI Q&A

2026-05-06

EPSS Evaluated

2026-07-04

NVD

CVE-2026-43111

EUVD

EUVD-2026-27633

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	7.0
linux	linux_kernel	7.0
linux	linux_kernel	7.0
linux	linux_kernel	7.0
linux	linux_kernel	7.0
linux	linux_kernel	7.0
linux	linux_kernel	7.0
linux	linux_kernel	From 6.13 (inc) to 6.18.24 (exc)
linux	linux_kernel	From 6.19 (inc) to 6.19.14 (exc)
linux	linux_kernel	From 6.7 (inc) to 6.12.83 (exc)
linux	linux_kernel	From 2.6.35 (inc) to 6.6.136 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-416	The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

Attack-Flow Graph

Executive Summary

This vulnerability exists in the Linux kernel's handling of roccat devices. Specifically, the function roccat_report_event() iterates over a list of device readers without holding the necessary readers_lock mutex. Because of this, another function, roccat_release(), can concurrently remove and free a reader from the list while it is still being accessed. This leads to a use-after-free condition, which is a type of memory error where the system accesses memory that has already been freed.

Impact Analysis

The use-after-free vulnerability can lead to undefined behavior in the Linux kernel, including potential system crashes, data corruption, or exploitation by attackers to execute arbitrary code with kernel privileges. This can compromise system stability and security.

Hi! I’m here to help you understand CVE-2026-43111. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70