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.
Author | Note |
---|---|
rodrigo-zaiden | USN-6765-1 for linux-oem-6.5 wrongly stated that this CVE was fixed in version 6.5.0-1022.23. The mentioned notice was revoked and the state of the fix for linux-oem-6.5 was recovered to the previous state. |
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
ubuntu | 20.04 | noarch | linux | < 5.4.0-181.201 | UNKNOWN |
ubuntu | 22.04 | noarch | linux | < 5.15.0-106.116 | UNKNOWN |
ubuntu | 23.10 | noarch | linux | < 6.5.0-41.41 | UNKNOWN |
ubuntu | 20.04 | noarch | linux-aws | < 5.4.0-1124.134 | UNKNOWN |
ubuntu | 22.04 | noarch | linux-aws | < 5.15.0-1061.67 | UNKNOWN |
ubuntu | 23.10 | noarch | linux-aws | < 6.5.0-1021.21 | UNKNOWN |
ubuntu | 20.04 | noarch | linux-aws-5.15 | < 5.15.0-1061.67~20.04.1 | UNKNOWN |
ubuntu | 18.04 | noarch | linux-aws-5.4 | < 5.4.0-1124.134~18.04.1 | UNKNOWN |
ubuntu | 22.04 | noarch | linux-aws-6.5 | < any | UNKNOWN |
ubuntu | 20.04 | noarch | linux-azure | < 5.4.0-1129.136 | UNKNOWN |
git.kernel.org/linus/5266caaf5660529e3da53004b8b7174cab6374ed (6.8-rc1)
git.kernel.org/stable/c/1d9c777d3e70bdc57dddf7a14a80059d65919e56
git.kernel.org/stable/c/5266caaf5660529e3da53004b8b7174cab6374ed
git.kernel.org/stable/c/6d8b01624a2540336a32be91f25187a433af53a0
git.kernel.org/stable/c/7610ba1319253225a9ba8a9d28d472fc883b4e2f
git.kernel.org/stable/c/89e0e66682e1538aeeaa3109503473663cd24c8b
git.kernel.org/stable/c/9525b38180e2753f0daa1a522b7767a2aa969676
git.kernel.org/stable/c/ecd7744a1446eb02ccc63e493e2eb6ede4ef1e10
git.kernel.org/stable/c/f1bc0d8163f8ee84a8d5affdf624cfad657df1d2
launchpad.net/bugs/cve/CVE-2024-26671
nvd.nist.gov/vuln/detail/CVE-2024-26671
security-tracker.debian.org/tracker/CVE-2024-26671
ubuntu.com/security/notices/USN-6766-1
ubuntu.com/security/notices/USN-6766-2
ubuntu.com/security/notices/USN-6766-3
ubuntu.com/security/notices/USN-6767-1
ubuntu.com/security/notices/USN-6767-2
ubuntu.com/security/notices/USN-6795-1
ubuntu.com/security/notices/USN-6818-1
ubuntu.com/security/notices/USN-6818-2
ubuntu.com/security/notices/USN-6818-3
ubuntu.com/security/notices/USN-6818-4
ubuntu.com/security/notices/USN-6819-1
ubuntu.com/security/notices/USN-6819-2
ubuntu.com/security/notices/USN-6819-3
ubuntu.com/security/notices/USN-6819-4
ubuntu.com/security/notices/USN-6828-1
www.cve.org/CVERecord?id=CVE-2024-26671