Loading vulnerability…
CVE-2024-35857 is a NULL-pointer dereference vulnerability in the Linux kernel ICMP subsystem's icmp_build_probe() path. The code could invoke __in_dev_get_rcu() twice while evaluating an IPv4 interface-address list, allowing the second lookup to return NULL before dereference. It also dereferenced the IPv6 device-address structure without first verifying that the associated pointer was non-NULL. The upstream correction uses the appropriate RCU access APIs and NULL-safe handling for these interface-address structures.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A potential NULL-pointer dereference vulnerability in the Linux kernel ICMP icmp_build_probe() function.
Linux kernel ICMP flaw that could result in null-pointer dereferences in icmp_build_probe().
A possible NULL-pointer dereference in the Linux kernel ICMP probe-building path.
Potential null-pointer dereference in the Linux kernel ICMP probe-building path.
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.