PT-2026-64561 · Linux · Linux
CVE-2026-64340
·
Published
2026-07-25
·
Updated
2026-07-25
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
In the Linux kernel, the following vulnerability has been resolved:
USB: legousbtower: 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")
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Linux