USB: iowarrior: fix use-after-free on disconnect race
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.97, 6.18.58, 7.1.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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")
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 946b960d13c15f050a3b848987aaca79f6a459b7 · fixed in 4e7d3c98fed73d3be84d3e146d8d9be0309e725b; From 946b960d13c15f050a3b848987aaca79f6a459b7 · fixed in 3c0a7b29ebb391d5f50b115e86f842b709195b08; From 946b960d13c15f050a3b848987aaca79f6a459b7 · fixed in 30ec3025b771511625375fb3fb959aea3b45fb0d; From 946b960d13c15f050a3b848987aaca79f6a459b7 · fixed in 71590982700fdeb39a37a500c877228b0140978e; From 946b960d13c15f050a3b848987aaca79f6a459b7 · fixed in c602254ba4c10f60a73cd99d147874f86a3f485c
- Linux Linux
2.6.21
- KernelLinux
From 2.6.21 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.97; From 6.13.0 · fixed in 6.18.58; From 6.19.0 · fixed in 7.1.4