CVE Catalog

CVE-2026-90180

Unknown
Published: Translated: NVD NIST

Summary

In the Linux kernel's mtip32xx driver, ioctl handlers are not synchronized with device removal. The REMOVE_PENDING bit is checked before entering mtip_hw_ioctl(), but removal can set it immediately afterwards and free dd->port while an ioctl still dereferences it, leading to a use-after-free.

Risk Assessment

A use-after-free may occur, leading to a kernel crash or potential privilege escalation. The risk occurs when a block device is removed while an ioctl is in progress.

Recommendation

Update the kernel to a version containing the fix that serializes ioctls with device removal. Until then, avoid concurrent device removal and ioctl operations on mtip32xx.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS