block: don't call rq_qos_ops->done_bio if the bio isn't tracked
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 004b8f8a691205a93d9e80d98b786b2b97424d6e, Kernel a647a524a46736786c95cdb553a070322ca096e3 and Kernel db60edbfff332a6a5477c367af8125f034570989.
In the Linux kernel, the following vulnerability has been resolved: block: don't call rq_qos_ops->done_bio if the bio isn't tracked rq_qos framework is only applied on request based driver, so: 1) rq_qos_done_bio() needn't to be called for bio based driver 2) rq_qos_done_bio() needn't to be called for bio which isn't tracked, such as bios ended from error handling code. Especially in bio_endio(): 1) request queue is referred via bio->bi_bdev->bd_disk->queue, which may be gone since request queue refcount may not be held in above two cases 2) q->rq_qos may be freed in blk_cleanup_queue() when calling into __rq_qos_done_bio() Fix the potential kernel panic by not calling rq_qos_ops->done_bio if the bio isn't tracked. This way is safe because both ioc_rqos_done_bio() and blkcg_iolatency_done_bio() are nop if the bio isn't tracked.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =4.19, >=67b42d0bf7a8fd1ec0cf1acdc9550e688d7c8578 <004b8f8a691205a93d9e80d98b786b2b97424d6e, >=67b42d0bf7a8fd1ec0cf1acdc9550e688d7c8578 <a647a524a46736786c95cdb553a070322ca096e3, >=67b42d0bf7a8fd1ec0cf1acdc9550e688d7c8578 <db60edbfff332a6a5477c367af8125f034570989 | 004b8f8a691205a93d9e80d98b786b2b97424d6e, a647a524a46736786c95cdb553a070322ca096e3, db60edbfff332a6a5477c367af8125f034570989 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket