Loading vulnerability…
CVE-2022-4129 is an improper resource-locking vulnerability in the Linux kernel Layer 2 Tunneling Protocol implementation. L2TP can clear socket user data while modifying the underlying tunnel socket without acquiring the required lock. Concurrent access can race with this operation, leaving state that is subsequently dereferenced as NULL and causing a kernel NULL-pointer dereference.
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.
Linux kernel L2TP locking flaw causing a NULL-pointer dereference.
Linux L2TP locking flaw causing a NULL-pointer dereference.
Linux kernel L2TP missing-lock flaw that can cause a NULL-pointer dereference.
Linux kernel L2TP locking flaw leading to a NULL-pointer dereference.
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.