Loading vulnerability…
A use-after-free vulnerability existed in the Linux kernel block multiqueue (blk-mq) subsystem during bio submission and cached request reuse. When blk-mq peeked a cached request for potential use, a task could sleep before actually popping that request from the cache. During that window, a plug flush could invoke request cleanup and free the cached request list, leaving the previously peeked request dangling. Subsequent use of that stale request created a use-after-free condition. The fix changes the logic so that a suitable cached request is popped before any potentially blocking call, ensuring the request is held with an active queue reference and can be safely dispatched without being freed concurrently.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A specific vulnerability affecting Red Hat Enterprise Linux 10.2 kernel-related packages; the content does not provide technical details beyond listing it in the advisory.
A Linux kernel vulnerability in blk-mq related to cached request handling.
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.