Loading vulnerability…
CVE-2026-43449 is an out-of-bounds read in the Linux kernel NVMe PCI driver’s doorbell-buffer setup path. The affected logic treats dev->online_queues, which is a queue count incremented during queue initialization, as though it were a valid array index boundary. Valid queue indices range from 0 through online_queues minus one; queue 0 is the administrative queue and should be excluded from the I/O-queue iteration. An incorrect loop condition permits access past the allocated queue-related array during nvme_dbbuf_set, including through the nvme_dbbuf_free path invoked while NVMe reset work is processed. KASAN detected a two-byte read beyond the allocated object.
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 valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
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.