Strix
26.1K

CVE-2026-64343

UnknownEPSS 0.18%

Last modified

CVE-2026-64343 is a vulnerability of currently unknown severity. 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"). EPSS estimates a 0.18% chance of exploitation in the next 30 days.

Description

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")

Metrics

EPSS Probability
0.18%

7.4th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= ce0d7d3f575fc1ba6a89c3c651e710355590daff, < fc55923a972e715f9a27187b47d4920709e23d85; >= ce0d7d3f575fc1ba6a89c3c651e710355590daff, < e5a9bdce4bfd3e2226b5f3df5fb8385d6935ee69; >= ce0d7d3f575fc1ba6a89c3c651e710355590daff, < af59829e67e11ba2511a9f8e4b9111afc7d1f550; >= ce0d7d3f575fc1ba6a89c3c651e710355590daff, < 02ca08fff74cf9b0a3c4d2cacde1c6edeeb95bb4; >= ce0d7d3f575fc1ba6a89c3c651e710355590daff, < d8f69404e1d671326f86d378b9f5bfbd56490e9d; >= ce0d7d3f575fc1ba6a89c3c651e710355590daff, < 2107a4fc8ff1cf1d52f416c1e5cc8e97413a5915; >= ce0d7d3f575fc1ba6a89c3c651e710355590daff, < a3e794136ab5e3ad1e7019175a4b837aec86db4b; >= ce0d7d3f575fc1ba6a89c3c651e710355590daff, < 19bdfc7b3c179331eafa423d87e1336f43bbfeb8
LinuxLinux2.6.26

References

Timeline

Published
Last Modified
Status
Awaiting Analysis

Frequently Asked Questions

What is CVE-2026-64343?
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")
How severe is CVE-2026-64343?
Severity scoring for CVE-2026-64343 is pending analysis. The EPSS model estimates a 0.18% probability of exploitation in the next 30 days.
How do I fix CVE-2026-64343?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-64343?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST