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
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
946b960d13c15f050a3b848987aaca79f6a459b7 to < 4e7d3c98fed73d3be84d3e146d8d9be0309e725baffected946b960d13c15f050a3b848987aaca79f6a459b7 to < 3c0a7b29ebb391d5f50b115e86f842b709195b08affected946b960d13c15f050a3b848987aaca79f6a459b7 to < 30ec3025b771511625375fb3fb959aea3b45fb0daffected946b960d13c15f050a3b848987aaca79f6a459b7 to < 71590982700fdeb39a37a500c877228b0140978eaffected946b960d13c15f050a3b848987aaca79f6a459b7 to < c602254ba4c10f60a73cd99d147874f86a3f485caffected
Linux Linux
Default version status: affected
2.6.21affected0 to < 2.6.21unaffected6.6.160 to ≤ 6.6.*unaffected6.12.97 to ≤ 6.12.*unaffected6.18.58 to ≤ 6.18.*unaffected7.1.4 to ≤ 7.1.*unaffected7.2 to ≤ *unaffected
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 ↗