Loading vulnerability…
CVE-2024-35888 is an uninitialized-value vulnerability in Linux kernel ERSPAN receive processing. The IPv4 ERSPAN and IPv6 ERSPAN receive paths accessed the ERSPAN base-header version field without first ensuring that the complete base header was available in the linear portion of the socket buffer. For non-linear socket buffers, this can cause the kernel to consume uninitialized data. The fix adds pskb_may_pull() validation before accessing the header and reloads the IPv4 header pointer after the pull operation because socket-buffer head storage may change.
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.
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An insufficient packet-header presence check in Linux kernel ERSPAN processing.
A Linux kernel ERSPAN vulnerability involving validation that the ERSPAN base header is present in the packet buffer head.
Linux kernel ERSPAN packet header bounds-validation vulnerability.
Linux kernel ERSPAN base-header presence validation flaw.
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.