Loading vulnerability…
CVE-2021-46984 is an out-of-bounds read in the Linux kernel's Kyber block I/O scheduler. During bio merging, __blk_mq_sched_bio_merge() obtains a CPU context and hardware context, then invokes kyber_bio_merge(). If the executing thread is preempted before Kyber obtains the CPU context again, the newly obtained context can belong to a different hardware context than the one passed to Kyber. Kyber may then use an index exceeding the passed hardware context's context count, resulting in an invalid array access and reads of unintended memory. The defect was observed as a UBSAN array-index-out-of-bounds condition during Kyber I/O merging.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel out-of-bounds access flaw in Kyber.
An out-of-bounds read vulnerability in the Linux kernel Kyber I/O scheduler. A thread preempted between context lookups can cause Kyber to pair a context with the wrong hardware context, potentially reading garbage or beyond the context array bounds.
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.