block: mtip32xx: synchronize ioctls with device removal
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 88523a61558a040546bf7d8b079ae0755d8e7005 · < 68940f841d013192086a0f6d7cfbac2cd079e228| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
block: mtip32xx: synchronize ioctls with device removal
The ioctl handlers only test REMOVE_PENDING before entering mtip_hw_ioctl(). Removal can set that bit immediately afterwards and free dd->port in mtip_hw_exit() while an ioctl still dereferences it. An already open block device can reach the handlers while del_gendisk() is in progress.
Serialize both native and compat ioctls with removal. Set REMOVE_PENDING before taking the mutex so new callers fail after an in-flight ioctl has drained, and hold the mutex until the port has been torn down.
From the CVE record · Linux
The Linux kernel's mtip32xx ioctl handlers can access a port after device removal frees it. A local caller with an already open block device can reach the handlers while removal is in progress; the input does not specify authentication requirements.
Engineers running Linux kernels with the mtip32xx block driver should check their installations; affected versions are not specified.