VulnerabilityPublished 25 Jul 2026Updated 6 Nov 2026

CVE-2026-64343: Linux kernel · USB: ldusb: fix use-after-free on disconnect race

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in fc55923a972e715f9a27187b47d4920709e23d85 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:04 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch

Available – fixed in fc55923a972e715f9a27187b47d4920709e23d85, e5a9bdce4bfd3e2226b5f3df5fb8385d6935ee69, d8f69404e1d671326f86d378b9f5bfbd56490e9d +5

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ ce0d7d3f575fc1ba6a89c3c651e710355590daff, < fc55923a972e715f9a27187b47d4920709e23d85	Fixed in fc55923a972e715f9a27187b47d4920709e23d85
LinuxLinux	Affected ≥ ce0d7d3f575fc1ba6a89c3c651e710355590daff, < e5a9bdce4bfd3e2226b5f3df5fb8385d6935ee69	Fixed in e5a9bdce4bfd3e2226b5f3df5fb8385d6935ee69
LinuxLinux	Affected ≥ ce0d7d3f575fc1ba6a89c3c651e710355590daff, < d8f69404e1d671326f86d378b9f5bfbd56490e9d	Fixed in d8f69404e1d671326f86d378b9f5bfbd56490e9d
LinuxLinux	Affected ≥ ce0d7d3f575fc1ba6a89c3c651e710355590daff, < af59829e67e11ba2511a9f8e4b9111afc7d1f550	Fixed in af59829e67e11ba2511a9f8e4b9111afc7d1f550
LinuxLinux	Affected ≥ ce0d7d3f575fc1ba6a89c3c651e710355590daff, < a3e794136ab5e3ad1e7019175a4b837aec86db4b	Fixed in a3e794136ab5e3ad1e7019175a4b837aec86db4b
LinuxLinux	Affected ≥ ce0d7d3f575fc1ba6a89c3c651e710355590daff, < 2107a4fc8ff1cf1d52f416c1e5cc8e97413a5915	Fixed in 2107a4fc8ff1cf1d52f416c1e5cc8e97413a5915

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")

References

Community reviews

Loading reviews…