CVE-2024-26671: blk-mq: fix IO hang from sbitmap wakeup race
First published: Tue Apr 02 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: blk-mq: fix IO hang from sbitmap wakeup race In blk_mq_mark_tag_wait(), __add_wait_queue() may be re-ordered with the following blk_mq_get_driver_tag() in case of getting driver tag failure. Then in __sbitmap_queue_wake_up(), waitqueue_active() may not observe the added waiter in blk_mq_mark_tag_wait() and wake up nothing, meantime blk_mq_mark_tag_wait() can't get driver tag successfully. This issue can be reproduced by running the following test in loop, and fio hang can be observed in < 30min when running it on my test VM in laptop. modprobe -r scsi_debug modprobe scsi_debug delay=0 dev_size_mb=4096 max_queue=1 host_max_queue=1 submit_queues=4 dev=`ls -d /sys/bus/pseudo/drivers/scsi_debug/adapter*/host*/target*/*/block/* | head -1 | xargs basename` fio --filename=/dev/"$dev" --direct=1 --rw=randrw --bs=4k --iodepth=1 \ --runtime=100 --numjobs=40 --time_based --name=test \ --ioengine=libaio Fix the issue by adding one explicit barrier in blk_mq_mark_tag_wait(), which is just fine in case of running out of tag.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/kernel | <4.19.307 | 4.19.307 |
| redhat/kernel | <5.4.269 | 5.4.269 |
| redhat/kernel | <5.10.210 | 5.10.210 |
| redhat/kernel | <5.15.149 | 5.15.149 |
| redhat/kernel | <6.1.77 | 6.1.77 |
| redhat/kernel | <6.6.16 | 6.6.16 |
| redhat/kernel | <6.7.4 | 6.7.4 |
| redhat/kernel | <6.8 | 6.8 |
| debian/linux | 5.10.223-1 5.10.226-1 6.1.123-1 6.1.119-1 6.12.10-1 6.12.11-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/1d9c777d3e70bdc57dddf7a14a80059d65919e56
- https://git.kernel.org/stable/c/5266caaf5660529e3da53004b8b7174cab6374ed
- https://git.kernel.org/stable/c/6d8b01624a2540336a32be91f25187a433af53a0
- https://git.kernel.org/stable/c/7610ba1319253225a9ba8a9d28d472fc883b4e2f
- https://git.kernel.org/stable/c/89e0e66682e1538aeeaa3109503473663cd24c8b
- https://git.kernel.org/stable/c/9525b38180e2753f0daa1a522b7767a2aa969676
- https://git.kernel.org/stable/c/ecd7744a1446eb02ccc63e493e2eb6ede4ef1e10
- https://git.kernel.org/stable/c/f1bc0d8163f8ee84a8d5affdf624cfad657df1d2
- https://launchpad.net/bugs/cve/CVE-2024-26671
- https://access.redhat.com/security/cve/CVE-2024-26671
- https://lore.kernel.org/linux-cve-announce/2024040219-CVE-2024-26671-2543@gregkh/T
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2272812
- https://access.redhat.com/errata/RHSA-2024:2950
- https://access.redhat.com/errata/RHSA-2024:3138
- https://access.redhat.com/errata/RHSA-2024:8614
- https://access.redhat.com/errata/RHSA-2024:8613
- https://access.redhat.com/errata/RHSA-2024:9943
- https://access.redhat.com/errata/RHSA-2024:9942
- https://access.redhat.com/errata/RHSA-2024:10262
- https://bugzilla.redhat.com/show_bug.cgi?id=2272811
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-26671
- https://nvd.nist.gov/vuln/detail/CVE-2024-26671
- https://security-tracker.debian.org/tracker/CVE-2024-26671
- https://ubuntu.com/security/CVE-2024-26671
- https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html
- https://lists.debian.org/debian-lts-announce/2024/06/msg00020.html
- https://git.kernel.org/linus/5266caaf5660529e3da53004b8b7174cab6374ed
Frequently Asked Questions
What is the severity of CVE-2024-26671?
CVE-2024-26671 is considered a medium severity vulnerability affecting the Linux kernel.
How do I fix CVE-2024-26671?
To fix CVE-2024-26671, update the Linux kernel to the fixed versions specified in the vulnerability details.
Which Linux kernel versions are affected by CVE-2024-26671?
CVE-2024-26671 affects various versions of the Linux kernel, including versions prior to 4.19.307, 5.4.269, 5.10.210, 5.15.149, 6.1.77, 6.6.16, 6.7.4, and 6.8.
What type of systems are impacted by CVE-2024-26671?
Systems running vulnerable versions of the Linux kernel on Red Hat and Debian distributions are impacted by CVE-2024-26671.
What are the potential consequences of CVE-2024-26671?
Exploiting CVE-2024-26671 may lead to an IO hang due to race conditions in the block layer of the Linux kernel.
- agent/title
- agent/type
- agent/author
- agent/remedy
- agent/first-publish-date
- collector/launchpad-cve
- source/Launchpad
- agent/severity
- collector/nvd-api
- source/NVD
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2024-26671
- agent/software-canonical-lookup
- collector/usn-cve
- source/Ubuntu
- agent/description
- agent/event
- collector/nvd-cve
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/references
- agent/trending
- agent/tags
- collector/security-tracker-debian
- source/Debian
- agent/softwarecombine
- agent/source
- package-manager/redhat
- package-manager/debian