VulnerabilityPublished 25 Jul 2026Updated 21 Oct 2026

CVE-2026-64341: Linux kernel · USB: iowarrior: fix use-after-free on disconnect race

Affects Linux kernelSource CVE Database V5

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

Data as of 26 Oct 2026, 13:47 UTC

Severity

Unrated

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in c602254ba4c10f60a73cd99d147874f86a3f485c, 71590982700fdeb39a37a500c877228b0140978e, 30ec3025b771511625375fb3fb959aea3b45fb0d +2

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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 ≥ 946b960d13c15f050a3b848987aaca79f6a459b7, < c602254ba4c10f60a73cd99d147874f86a3f485c	Fixed in c602254ba4c10f60a73cd99d147874f86a3f485c
LinuxLinux	Affected ≥ 946b960d13c15f050a3b848987aaca79f6a459b7, < 71590982700fdeb39a37a500c877228b0140978e	Fixed in 71590982700fdeb39a37a500c877228b0140978e
LinuxLinux	Affected ≥ 946b960d13c15f050a3b848987aaca79f6a459b7, < 30ec3025b771511625375fb3fb959aea3b45fb0d	Fixed in 30ec3025b771511625375fb3fb959aea3b45fb0d
LinuxLinux	Affected ≥ 946b960d13c15f050a3b848987aaca79f6a459b7, < 4e7d3c98fed73d3be84d3e146d8d9be0309e725b	Fixed in 4e7d3c98fed73d3be84d3e146d8d9be0309e725b
LinuxLinux	Affected ≥ 946b960d13c15f050a3b848987aaca79f6a459b7, < 3c0a7b29ebb391d5f50b115e86f842b709195b08	Fixed in 3c0a7b29ebb391d5f50b115e86f842b709195b08
LinuxLinux	Affected =2.6.21	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: 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…