Tracker / CVE-2026-64344
CVE-2026-64344
High 7.8
In the Linux kernel, the following vulnerability has been resolved: USB: idmouse: fix use-after-free on disconnect race mutex_unlock() may access the mutex structure after releasing the lock and therefore cannot be used to manage lifetime of objects directly (unlike spinlocks and refcounts). [1][2] Use a kref to release the driver data to avoid use-after-free in mutex_unlock() when release() races with disconnect(). [1] a51749ab34d9 ("locking/mutex: Document that mutex_unlock() is non-atomic") [2] 2b9d9e0a9ba0 ("locking/mutex: Clarify that mutex_unlock(), and most other sleeping locks, can still use the lock object after it's unlocked")
Affected products and versions
| linux | linux_kernel |
|---|---|
| linux | linux_kernel · 2.6.24.1 → 5.10.261 |
| linux | linux_kernel · 5.11 → 5.15.212 |
| linux | linux_kernel · 5.16 → 6.1.178 |
| linux | linux_kernel · 6.13 → 6.18.39 |
| linux | linux_kernel · 6.19 → 7.1.4 |
| linux | linux_kernel · 6.2 → 6.6.145 |
| linux | linux_kernel · 6.7 → 6.12.96 |
Analysis
This page is not indexable yet.Until it carries original analysis — what it actually exposes, how to check in two minutes whether a system was touched, what to do if it was — the page stays noindex. The database decides that, not the template.