Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-26671: blk-mq: fix IO hang from sbitmap wakeup race

Noroxi assessment

Priority: Monitor (action score 18/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 1d9c777d3e70bdc57dddf7a14a80059d65919e56, 5266caaf5660529e3da53004b8b7174cab6374ed, 6d8b01624a2540336a32be91f25187a433af53a0.
  • Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 1d9c777d3e70bdc57dddf7a14a80059d65919e56, 5266caaf5660529e3da53004b8b7174cab6374ed, 6d8b01624a2540336a32be91f25187a433af53a0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 4.7 · v3.1—No exploit Fix available
Published
Apr 2, 2024
Updated
Oct 15, 2026
EPSS
0.1% · 8th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-26671

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux10.0
  • linux linux kernel4.20 and later · before 5.4.269
  • linux linux kernel5.5 and later · before 5.10.210
  • linux linux kernelbefore 4.19.307
  • linux linux kernel5.16 and later · before 6.1.77
  • linux linux kernel6.2 and later · before 6.7.4
  • linux linux kernel5.11 and later · before 5.15.149

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.11affected
    • da55f2cc78418dee88400aafbbaed19d7ac8188e and later · before 9525b38180e2753f0daa1a522b7767a2aa969676affected · git
    • da55f2cc78418dee88400aafbbaed19d7ac8188e and later · before ecd7744a1446eb02ccc63e493e2eb6ede4ef1e10affected · git
    • da55f2cc78418dee88400aafbbaed19d7ac8188e and later · before 7610ba1319253225a9ba8a9d28d472fc883b4e2faffected · git
    • da55f2cc78418dee88400aafbbaed19d7ac8188e and later · before 89e0e66682e1538aeeaa3109503473663cd24c8baffected · git
    • da55f2cc78418dee88400aafbbaed19d7ac8188e and later · before 1d9c777d3e70bdc57dddf7a14a80059d65919e56affected · git
    • da55f2cc78418dee88400aafbbaed19d7ac8188e and later · before 6d8b01624a2540336a32be91f25187a433af53a0affected · git
    • da55f2cc78418dee88400aafbbaed19d7ac8188e and later · before f1bc0d8163f8ee84a8d5affdf624cfad657df1d2affected · git
    • da55f2cc78418dee88400aafbbaed19d7ac8188e and later · before 5266caaf5660529e3da53004b8b7174cab6374edaffected · git
    • before 4.11not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.82-16.1.82-1
Debian:13linuxbefore 6.7.7-16.7.7-1
Red Hat:rhel_e4s:9.0::appstreambpftool-debuginfobefore 0:5.14.0-70.121.1.el9_00:5.14.0-70.121.1.el9_0
Red Hat:rhel_e4s:9.0::appstreamkernel-debug-debuginfobefore 0:5.14.0-70.121.1.el9_00:5.14.0-70.121.1.el9_0
Red Hat:rhel_e4s:9.0::appstreamkernel-debug-develbefore 0:5.14.0-70.121.1.el9_00:5.14.0-70.121.1.el9_0
Red Hat:rhel_e4s:9.0::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-70.121.1.el9_00:5.14.0-70.121.1.el9_0
Red Hat:rhel_e4s:9.0::appstreamkernel-debuginfobefore 0:5.14.0-70.121.1.el9_00:5.14.0-70.121.1.el9_0
Red Hat:rhel_e4s:9.0::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-70.121.1.el9_00:5.14.0-70.121.1.el9_0
Red Hat:rhel_e4s:9.0::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-70.121.1.el9_00:5.14.0-70.121.1.el9_0
Red Hat:rhel_e4s:9.0::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-70.121.1.el9_00:5.14.0-70.121.1.el9_0
Red Hat:rhel_e4s:9.0::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-70.121.1.el9_00:5.14.0-70.121.1.el9_0
Red Hat:rhel_e4s:9.0::appstreamkernel-develbefore 0:5.14.0-70.121.1.el9_00:5.14.0-70.121.1.el9_0
Red Hat:rhel_e4s:9.0::appstreamkernel-devel-matchedbefore 0:5.14.0-70.121.1.el9_00:5.14.0-70.121.1.el9_0
Red Hat:rhel_e4s:9.0::appstreamkernel-docbefore 0:5.14.0-70.121.1.el9_00:5.14.0-70.121.1.el9_0
Red Hat:rhel_e4s:9.0::appstreamkernel-tools-debuginfobefore 0:5.14.0-70.121.1.el9_00:5.14.0-70.121.1.el9_0
Red Hat:rhel_e4s:9.0::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-70.121.1.el9_00:5.14.0-70.121.1.el9_0
Red Hat:rhel_e4s:9.0::appstreamkernel-zfcpdump-develbefore 0:5.14.0-70.121.1.el9_00:5.14.0-70.121.1.el9_0
Red Hat:rhel_e4s:9.0::appstreamkernel-zfcpdump-devel-matchedbefore 0:5.14.0-70.121.1.el9_00:5.14.0-70.121.1.el9_0
Red Hat:rhel_e4s:9.0::appstreamperfbefore 0:5.14.0-70.121.1.el9_00:5.14.0-70.121.1.el9_0
Red Hat:rhel_e4s:9.0::appstreamperf-debuginfobefore 0:5.14.0-70.121.1.el9_00:5.14.0-70.121.1.el9_0
Red Hat:rhel_e4s:9.0::appstreampython3-perf-debuginfobefore 0:5.14.0-70.121.1.el9_00:5.14.0-70.121.1.el9_0
Red Hat:rhel_e4s:9.0::baseosbpftoolbefore 0:5.14.0-70.121.1.el9_00:5.14.0-70.121.1.el9_0
Red Hat:rhel_e4s:9.0::baseoskernelbefore 0:5.14.0-70.121.1.el9_00:5.14.0-70.121.1.el9_0
Red Hat:rhel_e4s:9.0::baseoskernel-abi-stablelistsbefore 0:5.14.0-70.121.1.el9_00:5.14.0-70.121.1.el9_0

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-26669Apr 2, 2024 · net/sched: flower: Fix chain template offload
    28Monitor
  • ← EarlierCVE-2024-26670Apr 2, 2024 · arm64: entry: fix ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD
    22Monitor
  • Later →CVE-2024-26677Apr 2, 2024 · rxrpc: Fix delayed ACKs to not set the reference serial number
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1d9c777d3e70bdc57dddf7a14a80059d65919e56Vendor (CNA)
Linux Linux5266caaf5660529e3da53004b8b7174cab6374edVendor (CNA)
Linux Linux6d8b01624a2540336a32be91f25187a433af53a0Vendor (CNA)
Linux Linux7610ba1319253225a9ba8a9d28d472fc883b4e2fVendor (CNA)
Linux Linux89e0e66682e1538aeeaa3109503473663cd24c8bVendor (CNA)
Linux Linux9525b38180e2753f0daa1a522b7767a2aa969676Vendor (CNA)
Linux Linuxecd7744a1446eb02ccc63e493e2eb6ede4ef1e10Vendor (CNA)
Linux Linuxf1bc0d8163f8ee84a8d5affdf624cfad657df1d2Vendor (CNA)
debian:linux6.1.82-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-modules0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-modules-extra0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debuginfo0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records