USB: iowarrior: fix use-after-free on disconnect race
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 946b960d13c15f050a3b848987aaca79f6a459b7 · < c602254ba4c10f60a73cd99d147874f86a3f485c| No fix yet |
| Linux Linux |
|
|
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")
From the CVE record · Linux
The Linux kernel USB iowarrior driver has a use-after-free vulnerability when release() races with disconnect(). The supplied description does not specify how an attacker could trigger the race or whether authentication, local access, or user interaction is required.
Engineers running Linux kernels with the USB iowarrior driver should check their versions; affected versions are not specified.