Loading vulnerability…
CVE-2024-42070 is an insufficient-validation vulnerability in the Linux kernel's netfilter nf_tables subsystem. Validation of NFT_DATA_VALUE when storing data to registers is conditional, although the datatype is always either NFT_DATA_VALUE or NFT_DATA_VERDICT. This validation gap can allow a pointer to a chain object to leak through nftables registers. The fix introduces a helper that infers the register type from the set datatype, allowing the unsafe conditional validation to be removed.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel netfilter nf_tables vulnerability involving conditional validation of NFT_DATA_VALUE when storing data to registers. Incomplete validation can leak a pointer to a chain object through the registers. The advisory rates it Medium, with a CVSS v3 base score of 5.5, and identifies affected Google Container-Optimized OS kernel packages.
Linux kernel Netfilter nftables input-validation flaw involving NFT_DATA_VALUE writes to data registers.
An insufficient validation flaw in Linux kernel Netfilter nf_tables when storing NFT_DATA_VALUE values in data registers.
Linux kernel nf_tables insufficient NFT_DATA_VALUE validation.
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.