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

Severity: high (CVSS 7.8 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.1% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-07-25 · updated 2026-10-30
Weakness: CWE-416

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

Affected products

Linux kernel: from 2.6.21.1 before 6.12.97; from 6.13 before 7.1.4; 2.6.21-rc2, 2.6.21-rc3, 2.6.21-rc4, 2.6.21-rc5, 2.6.21-rc6, 2.6.21-rc7 (+2); 2.6.21 — fixed in 6.12.97, 7.1.4
Linux: 2.6.21 — fixed in 7.2

How to fix

Upgrade to a fixed version: Linux kernel 6.12.97, 7.1.4; Linux 7.2. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-64341 or the next vulnerability affects your stack