CVE-2026-23272 is a vulnerability in the Linux kernel netfilter nf_tables subsystem. When an nf_tables set is full, the insertion path could publish a new set element and then remove it again without waiting for an RCU grace period, while an RCU reader might already be traversing that element. The issue is tied to element accounting and insertion ordering around set->nelems in the nf_tables set handling logic. The upstream fix changes the behavior to unconditionally bump set->nelems before insertion, always add the element transaction even when the set is full, and toggle a set_full flag so the operation returns -ENFILE and the abort path can safely unwind the set to its previous state. For element updates, set->nelems is decremented to restore the prior count. The vulnerability is therefore a race/concurrency flaw that can expose readers to an element that has been removed before RCU synchronization completes.
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.
25 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.