Description (CNA)
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 (CNA)
| Vendor / product | Versions |
|---|---|
| Linux / Linux | affected 946b960d13c15f050a3b848987aaca79f6a459b7 before 4e7d3c98fed73d3be84d3e146d8d9be0309e725b; affected 946b960d13c15f050a3b848987aaca79f6a459b7 before 3c0a7b29ebb391d5f50b115e86f842b709195b08; affected 946b960d13c15f050a3b848987aaca79f6a459b7 before 30ec3025b771511625375fb3fb959aea3b45fb0d; affected 946b960d13c15f050a3b848987aaca79f6a459b7 before 71590982700fdeb39a37a500c877228b0140978e; affected 946b960d13c15f050a3b848987aaca79f6a459b7 before c602254ba4c10f60a73cd99d147874f86a3f485c |
| Linux / Linux | affected 2.6.21; unaffected 0 before 2.6.21; unaffected 6.6.160 through 6.6.*; unaffected 6.12.97 through 6.12.*; unaffected 6.18.58 through 6.18.*; unaffected 7.1.4 through 7.1.*; unaffected 7.2 through * |
CWE
No CWE identifiers supplied.
References
- https://git.kernel.org/stable/c/4e7d3c98fed73d3be84d3e146d8d9be0309e725b
- https://git.kernel.org/stable/c/3c0a7b29ebb391d5f50b115e86f842b709195b08
- https://git.kernel.org/stable/c/30ec3025b771511625375fb3fb959aea3b45fb0d
- https://git.kernel.org/stable/c/71590982700fdeb39a37a500c877228b0140978e
- https://git.kernel.org/stable/c/c602254ba4c10f60a73cd99d147874f86a3f485c