CVE-2025-21826 is an input-validation flaw in the Linux kernel netfilter nf_tables pipapo set-processing path. Concatenated key fields are individually rounded to 32-bit boundaries when pipapo_init() calculates rule width, whereas the set key length is independently aligned to 32 bits. Register-based arithmetic could construct a set whose declared key length and field-length description are inconsistent; for example, a key length of 10 with field lengths of 5 and 4 produces a pipapo width of 12. The fix rejects configurations where the field-length total does not match the set key length.
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.
Linux kernel nftables key-length validation vulnerability.
Linux kernel nftables field-length validation vulnerability.
A Linux kernel netfilter nf_tables validation flaw where mismatched concatenated-field lengths and an aligned set-key length could be combined, producing an inconsistent pipapo rule width.
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.