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")
Affected versions
Linux kernel versions
2.6.25
and later are affected. Fixed in
5.10.261,
5.15.212,
6.1.178,
6.6.145,
6.12.96,
6.18.39,
7.1.4,
7.2-rc3
and their respective stable series.
References
8 totalFrequently asked questions
-
What is CVE-2026-64340?
CVE-2026-64340 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 2.6.25 onward and has been patched in 5.10.261, 5.15.212, 6.1.178 and others. CVE-2026-64340 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-64340?
Yes. CVE-2026-64340 has been patched. Fixed versions include 5.10.261, 5.15.212, 6.1.178 and others. If you are running Linux kernel 2.6.25 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-64340 actively exploited?
No. CVE-2026-64340 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.