ublk: fix use-after-free in ublk_partition_scan_work
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6.18.6, Kernel 72e28774e9644c2bdbb4920842fbf77103a15a85 and Kernel f0d385f6689f37a2828c686fb279121df006b4cb.
In the Linux kernel, the following vulnerability has been resolved: ublk: fix use-after-free in ublk_partition_scan_work A race condition exists between the async partition scan work and device teardown that can lead to a use-after-free of ub->ub_disk: 1. ublk_ctrl_start_dev() schedules partition_scan_work after add_disk() 2. ublk_stop_dev() calls ublk_stop_dev_unlocked() which does: - del_gendisk(ub->ub_disk) - ublk_detach_disk() sets ub->ub_disk = NULL - put_disk() which may free the disk 3. The worker ublk_partition_scan_work() then dereferences ub->ub_disk leading to UAF Fix this by using ublk_get_disk()/ublk_put_disk() in the worker to hold a reference to the disk during the partition scan. The spinlock in ublk_get_disk() synchronizes with ublk_detach_disk() ensuring the worker either gets a valid reference or sees NULL and exits early. Also change flush_work() to cancel_work_sync() to avoid running the partition scan work unnecessarily when the disk is already detached.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=6.18.4 <6.18.6, >=63dfbcd59b4b823eac4441efff10b1c303c8f49f <72e28774e9644c2bdbb4920842fbf77103a15a85, >=7fc4da6a304bdcd3de14fc946dc2c19437a9cc5a <f0d385f6689f37a2828c686fb279121df006b4cb | 6.18.6, 72e28774e9644c2bdbb4920842fbf77103a15a85, f0d385f6689f37a2828c686fb279121df006b4cb |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket