CVE-2024-27435 is a denial-of-service flaw in the Linux kernel NVMe subsystem affecting NVMe over RDMA controller recovery. During controller reset, the admin queue can be quiesced while a keep-alive request retains the sole reserved tag. Because the fabrics queue shares the admin queue tag set, a subsequent reconnect requires a reserved tag for the connect command but cannot obtain one. This circular resource dependency prevents admin-queue reconnection indefinitely even when the remote target and network are healthy. The upstream fix retains two reserved tags for the admin queue.
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 Linux kernel NVMe flaw that can cause reconnection failures due to reserved-tag allocation.
A Linux kernel NVMe vulnerability that can cause reconnection failure due to reserved-tag allocation.
A Linux kernel NVMe issue in which reserved tag allocation can cause reconnection failure. The content characterizes the potential impact as moderate, with automated flags indicating a possible deadlock.
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.