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.
Details
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| linux | — | 5.15.0-106.116 |
| linux-allwinner-5.19 | — | — |
| linux-aws | — | 5.15.0-1061.67 |
| linux-aws-5.0 | — | — |
| linux-aws-5.11 | — | — |
| linux-aws-5.13 | — | — |
| linux-aws-5.15 | — | 5.15.0-1061.67~20.04.1 |
| linux-aws-5.19 | — | — |
| linux-aws-5.3 | — | — |
| linux-aws-5.4 | — | 5.4.0-1124.134~18.04.1 |
| linux-aws-5.8 | — | — |
| linux-aws-6.2 | — | — |
| linux-aws-6.5 | — | — |
| linux-aws-fips | — | 5.15.0-1061.67+fips1 |
| linux-aws-hwe | — | — |
| linux-azure | — | 5.15.0-1063.72 |
| linux-azure-4.15 | — | — |
| linux-azure-5.11 | — | — |
| linux-azure-5.13 | — | — |
| linux-azure-5.15 | — | 5.15.0-1063.72~20.04.1 |
| linux-azure-5.19 | — | — |
| linux-azure-5.3 | — | — |
| linux-azure-5.4 | — | 5.4.0-1129.136~18.04.1 |
| linux-azure-5.8 | — | — |
| linux-azure-6.2 | — | — |
| linux-azure-6.5 | — | 6.5.0-1022.23~22.04.1 |
| linux-azure-edge | — | — |
| linux-azure-fde | — | — |
| linux-azure-fde-5.15 | — | — |
| linux-azure-fde-5.19 | — | — |
| linux-azure-fde-6.2 | — | — |
| linux-azure-fde-6.8 | — | — |
| linux-azure-fips | — | 5.15.0-1063.72+fips1 |
| linux-bluefield | — | — |
| linux-fips | — | 5.15.0-106.116+fips1 |
| linux-gcp | — | 5.15.0-1059.67 |
| linux-gcp-4.15 | — | — |
| linux-gcp-5.11 | — | — |
| linux-gcp-5.13 | — | — |
| linux-gcp-5.15 | — | 5.15.0-1059.67~20.04.1 |
| linux-gcp-5.19 | — | — |
| linux-gcp-5.3 | — | — |
| linux-gcp-5.4 | — | 5.4.0-1128.137~18.04.1 |
| linux-gcp-5.8 | — | — |
| linux-gcp-6.2 | — | — |
| linux-gcp-6.5 | — | 6.5.0-1022.24~22.04.1 |
| linux-gcp-fips | — | 5.15.0-1059.67+fips1 |
| linux-gke | — | 5.15.0-1058.63 |
| linux-gke-4.15 | — | — |
| linux-gke-5.15 | — | — |
| linux-gke-5.4 | — | — |
| linux-gkeop | — | 5.15.0-1044.51 |
| linux-gkeop-5.15 | — | 5.15.0-1044.51~20.04.1 |
| linux-gkeop-5.4 | — | — |
| linux-hwe | — | — |
| linux-hwe-5.11 | — | — |
| linux-hwe-5.13 | — | — |
| linux-hwe-5.15 | — | 5.15.0-106.116~20.04.1 |
| linux-hwe-5.19 | — | — |
| linux-hwe-5.4 | — | 5.4.0-181.201~18.04.1 |
| linux-hwe-5.8 | — | — |
| linux-hwe-6.2 | — | — |
| linux-hwe-6.5 | — | 6.5.0-41.41~22.04.2 |
| linux-hwe-edge | — | — |
| linux-ibm | — | 5.15.0-1054.57 |
| linux-ibm-5.15 | — | 5.15.0-1054.57~20.04.1 |
| linux-ibm-5.4 | — | 5.4.0-1071.76~18.04.1 |
| linux-intel-5.13 | — | — |
| linux-intel-iot-realtime | — | 5.15.0-1054.56 |
| linux-intel-iotg | — | 5.15.0-1057.63 |
| linux-intel-iotg-5.15 | — | 5.15.0-1058.64~20.04.1 |
| linux-iot | — | 5.4.0-1036.37 |
| linux-kvm | — | 5.15.0-1058.63 |
| linux-lowlatency | — | 5.15.0-106.116 |
| linux-lowlatency-hwe-5.15 | — | 5.15.0-106.116~20.04.1 |
| linux-lowlatency-hwe-5.19 | — | — |
| linux-lowlatency-hwe-6.2 | — | — |
| linux-lowlatency-hwe-6.5 | — | 6.5.0-41.41.1~22.04.1 |
| linux-lts-xenial | — | — |
| linux-nvidia | — | 5.15.0-1054.55 |
| linux-nvidia-6.2 | — | — |
| linux-nvidia-6.5 | — | 6.5.0-1021.22 |
| linux-nvidia-tegra | — | 5.15.0-1026.26 |
| linux-nvidia-tegra-5.15 | — | 5.15.0-1027.27~20.04.1 |
| linux-nvidia-tegra-igx | — | 5.15.0-1015.15 |
| linux-oem | — | — |
| linux-oem-5.10 | — | — |
| linux-oem-5.13 | — | — |
| linux-oem-5.14 | — | — |
| linux-oem-5.17 | — | — |
| linux-oem-5.6 | — | — |
| linux-oem-6.0 | — | — |
| linux-oem-6.1 | — | — |
| linux-oem-6.5 | — | 6.5.0-1024.25 |
| linux-oracle | — | 5.15.0-1059.65 |
| linux-oracle-5.0 | — | — |
| linux-oracle-5.11 | — | — |
| linux-oracle-5.13 | — | — |
| linux-oracle-5.15 | — | 5.15.0-1059.65~20.04.1 |
| linux-oracle-5.3 | — | — |
| linux-oracle-5.4 | — | 5.4.0-1123.132~18.04.1 |
| linux-oracle-5.8 | — | — |
| linux-oracle-6.5 | — | 6.5.0-1024.24~22.04.1 |
| linux-raspi | — | 5.15.0-1054.57 |
| linux-raspi-5.4 | — | 5.4.0-1108.120~18.04.1 |
| linux-raspi-realtime | — | 6.8.0-2001.1 |
| linux-raspi2 | — | — |
| linux-realtime | — | 5.15.0-1062.70 |
| linux-riscv | — | — |
| linux-riscv-5.11 | — | — |
| linux-riscv-5.15 | — | 5.15.0-1057.61~20.04.1 |
| linux-riscv-5.19 | — | — |
| linux-riscv-5.8 | — | — |
| linux-riscv-6.5 | — | 6.5.0-40.40.1~22.04.1 |
| linux-starfive-5.19 | — | — |
| linux-starfive-6.2 | — | — |
| linux-starfive-6.5 | — | 6.5.0-1015.16~22.04.1 |
| linux-xilinx-zynqmp | — | 5.15.0-1030.34 |
References
Similar Threats
- Unknown CGA-23jx-hhcx-m389
- Unknown CGA-2qp7-6757-fmgc
- Unknown CGA-2rj5-jc55-r267
- Unknown CGA-3m96-cwq8-6xmx
- Unknown CGA-3qj9-973w-fh9g
Site Security Check
Concerned your site may already be targeted?
BotEraser analyzes incoming traffic patterns and helps identify bot behavior consistent with known exploit attempts.
Check My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.
