In the Linux kernel, the following vulnerability has been resolved: USB: ldusb: fix use-after-free on disconnect race mutex_unlock() may access the… (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")
AI Analysis
Technical Summary
The Linux kernel contained a use-after-free vulnerability in the USB ldusb driver caused by improper handling of mutex_unlock(). Unlike spinlocks and refcounts, mutex_unlock() can access the mutex object after unlocking, making it unsafe to manage object lifetimes directly with it. This led to a race condition where release() could collide with disconnect(), potentially causing use-after-free. The vulnerability was fixed by employing a kref to manage the driver data's lifetime, preventing unsafe access after the mutex is unlocked.
Potential Impact
This vulnerability could lead to use-after-free conditions in the Linux kernel USB driver, potentially causing kernel crashes or undefined behavior. No known exploits are reported in the wild. The impact is limited to kernel stability and security related to USB device handling.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this vulnerability by using kref for driver data lifetime management. Users should apply the official kernel updates that include this fix. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: USB: ldusb: fix use-after-free on disconnect race mutex_unlock() may access the… (CVE-2026-64343)
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")
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel contained a use-after-free vulnerability in the USB ldusb driver caused by improper handling of mutex_unlock(). Unlike spinlocks and refcounts, mutex_unlock() can access the mutex object after unlocking, making it unsafe to manage object lifetimes directly with it. This led to a race condition where release() could collide with disconnect(), potentially causing use-after-free. The vulnerability was fixed by employing a kref to manage the driver data's lifetime, preventing unsafe access after the mutex is unlocked.
Potential Impact
This vulnerability could lead to use-after-free conditions in the Linux kernel USB driver, potentially causing kernel crashes or undefined behavior. No known exploits are reported in the wild. The impact is limited to kernel stability and security related to USB device handling.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this vulnerability by using kref for driver data lifetime management. Users should apply the official kernel updates that include this fix. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-fmwh-mr5j-p6wq
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64343"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a65420c9c2644c7f8085075
Added to database: 07/25/2026, 23:09:00 UTC
Last enriched: 07/25/2026, 23:32:27 UTC
Last updated: 09/07/2026, 10:52:10 UTC
Views: 59
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.