Loading vulnerability…
A vulnerability in the Linux kernel's netfilter flowtable component allowed insufficient validation of the PPPoE header. Specifically, the code did not ensure there was enough data to safely access the protocol field of the PPPoE header, potentially leading to out-of-bounds memory access. The issue was resolved by adding proper length checks before accessing the protocol field and using a helper function for safe access.
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.
Linux kernel netfilter flowtable PPPoE-header validation flaw.
Linux kernel netfilter flowtable flaw caused by inadequate PPPoE header validation.
Linux kernel netfilter flowtable PPPoE-header validation flaw.
Linux kernel Netfilter flowtable PPPoE-header 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.