Loading vulnerability…
CVE-2026-68121 is a Linux kernel PPPoE memory-safety vulnerability in pppoe_sendmsg(). The function retains a pointer to the PPPoE header before invoking dev_hard_header(). A device header callback may expand and relocate the socket-buffer head, invalidating pointers into the prior allocation. Subsequent PPPoE processing writes six bytes through the stale header pointer, potentially writing to freed skb-head memory. The fix reacquires the PPPoE header using the skb network-header offset after device header creation; that offset is maintained when the skb head is relocated.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux local privilege-escalation (local root) vulnerability referred to as TUNderflow.
A Linux kernel PPPoE issue requiring the header pointer to be reloaded after dev_hard_header(), fixed for SLES 11 SP4.
A medium-severity Linux kernel PPPoE vulnerability involving failure to reload a header pointer after dev_hard_header(). Amazon Linux assigns CVSS v3.1 score 4.7 (AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:H), indicating local exploitation with high attack complexity and high privileges, with integrity and availability impact.
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.