All reports
Medium

kernel: kernel: Denial of Service via race condition in hiddev driver

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-99474

Probability of exploitation in the next 30 days: 0.17%

FIRST EPSS · 2026-11-20

Description

In the Linux kernel, the following vulnerability has been resolved: HID: hiddev: keep state alive through disconnect unlock mutex_unlock() clears the mutex owner before taking its wait lock. A thread spinning in the final hiddev file release can acquire existancelock after hiddev_disconnect() clears the owner, then free hiddev before the disconnecting thread reaches the mutex wait lock. This causes a use-after-free in the mutex slow unlock path. Give the connection and each open file an explicit reference. Drop each reference only after its existancelock critical section has completed, so neither unlock path can free the mutex while the other is still using it.

A flaw was found in the Linux kernel's Human Interface Device (HID) subsystem. A race condition in the hiddev driver between disconnecting a device and closing its file descriptor allows shared memory to be freed while a lock is still being released. A local attacker could exploit this vulnerability to trigger a kernel crash, resulting in a Denial of Service (DoS).