blk-mq: fix blk_mq_tags double free while nr_requests grown
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 8faee580d63bc2a54a59dcdb7f9ce4de29384fec, Kernel 392b1d64911f4de8887fe8b68299fa8bd6e5b923, Kernel ba28afbd9eff2a6370f23ef4e6a036ab0cfda409 and 2 more.
In the Linux kernel, the following vulnerability has been resolved: blk-mq: fix blk_mq_tags double free while nr_requests grown In the case user trigger tags grow by queue sysfs attribute nr_requests, hctx->sched_tags will be freed directly and replaced with a new allocated tags, see blk_mq_tag_update_depth(). The problem is that hctx->sched_tags is from elevator->et->tags, while et->tags is still the freed tags, hence later elevator exit will try to free the tags again, causing kernel panic. Fix this problem by replacing et->tags with new allocated tags as well. Noted there are still some long term problems that will require some refactor to be fixed thoroughly[1]. [1] https://lore.kernel.org/all/20250815080216.410665-1-yukuai1@huaweicloud.com/
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=58567d8e95c096ad234963df90a2ca518901f4b6 <8faee580d63bc2a54a59dcdb7f9ce4de29384fec, >=f5a6604f7a4405450e4a1f54e5430f47290c500f <392b1d64911f4de8887fe8b68299fa8bd6e5b923, >=f5a6604f7a4405450e4a1f54e5430f47290c500f <ba28afbd9eff2a6370f23ef4e6a036ab0cfda409, =6.17, >=6.16.4 <6.16.11 | 8faee580d63bc2a54a59dcdb7f9ce4de29384fec, 392b1d64911f4de8887fe8b68299fa8bd6e5b923, ba28afbd9eff2a6370f23ef4e6a036ab0cfda409, 6.16.11 |
| linux-kernel: Kernel | >=6.17.0 <6.17.1, >=6.16.4 <6.16.11 | 6.17.1, 6.16.11 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket