CVE-2026-23278 is a Linux kernel vulnerability in the netfilter nf_tables subsystem. During nftables transaction processing, more than one catchall element can exist simultaneously, specifically one live catchall element and one pending catchall element introduced in the same batch. When the map containing those catchall elements is also being removed, the abort/cleanup logic failed to walk and toggle all pending catchall elements and instead handled only the first viable candidate. This leaves nf_tables state inconsistent during rollback and cleanup, leading to warnings in nft_data_release() and a faulty destruction path visible through call traces including __nft_set_elem_destroy(), nf_tables_abort_release(), nf_tables_abort(), and nfnetlink_rcv_batch(). The issue was resolved by changing nf_tables to always walk all pending catchall elements.
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.
16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A related Linux kernel bug spawned by the same break statement as CVE-2026-23111 and patched separately.
A specific vulnerability identified as CVE-2026-23278 is referenced in the context of a kernelCTF branch or exploit-related workflow, but no technical details about the flaw are provided in the content.
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.