Strix
26.1K

CVE-2026-64344

UnknownEPSS 0.18%

Last modified

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

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>= 54d2bc068fd21bcb096660938bce7c7265613a24, < 31e75fed8f90cfea9f8285e7ed135b0e452bf872; >= 54d2bc068fd21bcb096660938bce7c7265613a24, < 8d53b14ad4ccbff6d306b3a39c812303f4a87d41; >= 54d2bc068fd21bcb096660938bce7c7265613a24, < f62622e947f82a3854a8502d09492ffbdeb252b4; >= 54d2bc068fd21bcb096660938bce7c7265613a24, < 60fc5ef4ecea3e3d1fe556cecf53ddd13096ef09; >= 54d2bc068fd21bcb096660938bce7c7265613a24, < d0f61acb51a8c8f3fd41c303ddb7770cd83e7ed4; >= 54d2bc068fd21bcb096660938bce7c7265613a24, < 54c2b7356b4aeea467f9fb13b85e9e036bc428cb; >= 54d2bc068fd21bcb096660938bce7c7265613a24, < e88cff5fbaa629f3cab45c8b46f395d62c2eb515; >= 54d2bc068fd21bcb096660938bce7c7265613a24, < ff002c153f9722caece3983cc23dc4d9d4652cb4
LinuxLinux2.6.24

References

Timeline

Published
Last Modified
Status
Awaiting Analysis

Frequently Asked Questions

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

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

Scan your code now

Source: NVD / NIST