Kernel disruption via ldusb disconnect race
Published Jul 25, 2026 · Updated Jul 25, 2026
Use-after-free in the Linux Kernel ldusb driver allows local users to disrupt the kernel by racing device release with USB disconnect. The ldusb release path unlocks its mutex while disconnect can free the same driver data, and mutex_unlock() can still touch that freed lock object. Reaching the race requires access to an ldusb-backed device and concurrent release and disconnect activity; the published impact assessment is limited to availability.
Summary
What happened
Use-after-free in the Linux Kernel ldusb driver allows local users to disrupt the kernel by racing device release with USB disconnect. The ldusb release path unlocks its mutex while disconnect can free the same driver data, and mutex_unlock() can still touch that freed lock object. Reaching the race requires access to an ldusb-backed device and concurrent release and disconnect activity; the published impact assessment is limited to availability.
The record
- CVE
- CVE-2026-64343
- Published
- Jul 25, 2026
- Updated
- Jul 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 25, 2026CVE publishedPublication date reported by the CVE source.
- Jul 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.26
- Affected versionversion=ce0d7d3f575fc1ba6a89c3c651e710355590daff <02ca08fff74cf9b0a3c4d2cacde1c6edeeb95bb4
- Affected versionversion=ce0d7d3f575fc1ba6a89c3c651e710355590daff <19bdfc7b3c179331eafa423d87e1336f43bbfeb8
- Affected versionversion=ce0d7d3f575fc1ba6a89c3c651e710355590daff <2107a4fc8ff1cf1d52f416c1e5cc8e97413a5915
- Affected versionversion=ce0d7d3f575fc1ba6a89c3c651e710355590daff <a3e794136ab5e3ad1e7019175a4b837aec86db4b
- Affected versionversion=ce0d7d3f575fc1ba6a89c3c651e710355590daff <af59829e67e11ba2511a9f8e4b9111afc7d1f550
- Affected versionversion=ce0d7d3f575fc1ba6a89c3c651e710355590daff <d8f69404e1d671326f86d378b9f5bfbd56490e9d
- Affected versionversion=ce0d7d3f575fc1ba6a89c3c651e710355590daff <e5a9bdce4bfd3e2226b5f3df5fb8385d6935ee69
- Affected versionversion=ce0d7d3f575fc1ba6a89c3c651e710355590daff <fc55923a972e715f9a27187b47d4920709e23d85
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo