CVE-2026-99474
What it is
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.
At a glance
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: not scored yet.
- Severity: not scored yet.
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Record status
- Received
Affected
- Linux < 81e3e5ae4228f95414665877f5e487917fbef9c0
- Linux < 1b7b31f0d4bbfb9a87dd8acce1e001a3cf1c1623
- Linux < f214e9fe86a0aba6deb4a0b31b9998fb2b6879b5
- Linux < 03f449b5de36a25fc5eba7dabf2b4494389bdb91
- Linux 2.6.29
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-99474.md and follow it. Check whether this project is affected by CVE-2026-99474. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.