Strix
26.1K

CVE-2026-64340

UnknownEPSS 0.18%

Last modified

CVE-2026-64340 is a vulnerability of currently unknown severity. 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"). 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: 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")

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>= 18bcbcfe9ca2308ebffb40068b51803da9315d97, < 11d069f85851997b4ea0adf242ed9672dc749b8f; >= 18bcbcfe9ca2308ebffb40068b51803da9315d97, < b4222c05066b252b451f9c8c4730b5b60824ea66; >= 18bcbcfe9ca2308ebffb40068b51803da9315d97, < 6462de75d2e370c7e74dcfb7b4ae79eb5a6a55ee; >= 18bcbcfe9ca2308ebffb40068b51803da9315d97, < 0b57e5ddbd89df3bc367463de3d2ca66f99a1a5e; >= 18bcbcfe9ca2308ebffb40068b51803da9315d97, < ab2bfd7bec4f134b377ec42f513e90c35db94160; >= 18bcbcfe9ca2308ebffb40068b51803da9315d97, < 766738ecf2b819e54d38763c8d1c8ae6cff14b39; >= 18bcbcfe9ca2308ebffb40068b51803da9315d97, < 9ba62966461a8e3cc593b62c56ec62eb2d80436d; >= 18bcbcfe9ca2308ebffb40068b51803da9315d97, < 62fc8eb1b1481051f7bab4aa93d79809053dd09f
LinuxLinux2.6.25

References

Timeline

Published
Last Modified
Status
Awaiting Analysis

Frequently Asked Questions

What is CVE-2026-64340?
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")
How severe is CVE-2026-64340?
Severity scoring for CVE-2026-64340 is pending analysis. The EPSS model estimates a 0.18% probability of exploitation in the next 30 days.
How do I fix CVE-2026-64340?
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-64340?

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

Scan your code now

Source: NVD / NIST