CVE-2024-26671
Last modified
CVE-2024-26671 is a medium-severity vulnerability rated 4.7/10 on the CVSS scale. 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.. EPSS estimates a 0.19% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | < 4.19.307 |
| Linux | Linux Kernel | >= 4.20, < 5.4.269 |
| Linux | Linux Kernel | >= 5.5, < 5.10.210 |
| Linux | Linux Kernel | >= 5.11, < 5.15.149 |
| Linux | Linux Kernel | >= 5.16, < 6.1.77 |
| Linux | Linux Kernel | >= 6.2, < 6.7.4 |
| Debian | Debian Linux | 10.0 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2024-26671?
How severe is CVE-2024-26671?
How do I fix CVE-2024-26671?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-26666In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2024-26667In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26668In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26669In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2024-2667The InstaWP Connect – 1-click WP Staging & Migration plugin …9.8
- CVE-2024-26670In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26672In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2024-26673In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2024-26674In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2024-26675In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26676In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26677In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2024-26671?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
