Loading vulnerability…
CVE-2024-26671 is a race condition in the Linux kernel blk-mq block multi-queue subsystem. In blk_mq_mark_tag_wait(), adding a wait-queue entry can be reordered relative to a subsequent failed driver-tag acquisition. The sbitmap wake-up path can consequently fail to observe the newly added waiter and issue no wake-up, leaving the waiter unable to acquire a driver tag and causing I/O to hang. The upstream correction adds an explicit memory barrier in blk_mq_mark_tag_wait() for driver-tag exhaustion.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel blk-mq race condition in sbitmap waiter wakeup handling that can cause driver-tag acquisition to stall and result in an I/O hang, such as fio hanging under concurrent I/O load.
Linux kernel blk-mq sbitmap wakeup race that can cause I/O hangs.
Linux kernel block multi-queue I/O hang caused by an sbitmap wakeup race.
A race condition in the Linux kernel blk-mq block I/O subsystem that can cause an I/O hang during sbitmap wakeup processing.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.