CVE-2026-64343

Summary

In the Linux kernel, the following vulnerability has been resolved:

USB: ldusb: 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 Software

VendorProductVersion RangeStatus
LinuxLinuxce0d7d3f575fc1ba6a89c3c651e710355590daff < fc55923a972e715f9a27187b47d4920709e23d85affected
LinuxLinuxce0d7d3f575fc1ba6a89c3c651e710355590daff < e5a9bdce4bfd3e2226b5f3df5fb8385d6935ee69affected
LinuxLinuxce0d7d3f575fc1ba6a89c3c651e710355590daff < af59829e67e11ba2511a9f8e4b9111afc7d1f550affected
LinuxLinuxce0d7d3f575fc1ba6a89c3c651e710355590daff < 02ca08fff74cf9b0a3c4d2cacde1c6edeeb95bb4affected
LinuxLinuxce0d7d3f575fc1ba6a89c3c651e710355590daff < d8f69404e1d671326f86d378b9f5bfbd56490e9daffected
LinuxLinuxce0d7d3f575fc1ba6a89c3c651e710355590daff < 2107a4fc8ff1cf1d52f416c1e5cc8e97413a5915affected
LinuxLinuxce0d7d3f575fc1ba6a89c3c651e710355590daff < a3e794136ab5e3ad1e7019175a4b837aec86db4baffected
LinuxLinuxce0d7d3f575fc1ba6a89c3c651e710355590daff < 19bdfc7b3c179331eafa423d87e1336f43bbfeb8affected
LinuxLinux2.6.26affected
LinuxLinux0 < 2.6.26unaffected
LinuxLinux5.10.261 <= 5.10.*unaffected
LinuxLinux5.15.212 <= 5.15.*unaffected
LinuxLinux6.1.178 <= 6.1.*unaffected
LinuxLinux6.6.145 <= 6.6.*unaffected
LinuxLinux6.12.96 <= 6.12.*unaffected
LinuxLinux6.18.39 <= 6.18.*unaffected
LinuxLinux7.1.4 <= 7.1.*unaffected
LinuxLinux7.2-rc3 <= *unaffected

Weaknesses

References