CVE-2026-31411 is an untrusted pointer dereference vulnerability in the Linux kernel ATM networking subsystem. The sendmsg() → vcc_sendmsg() → sigd_send() path reads a VCC pointer from userspace-controlled msg->vcc and dereferences it without validating that it identifies an existing VCC. During normal operation, the ATM signaling daemon returns pointers previously supplied by the kernel through sigd_enq(). A malicious signaling daemon can instead submit an arbitrary pointer, causing a kernel crash. The flaw was introduced in Linux 2.6.12.
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.
16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel ATM networking vulnerability that can cause a crash due to an unvalidated VCC pointer in sigd_send().
A Linux kernel network/ATM flaw in sigd_send() caused by an unvalidated vcc pointer, which can result in a crash and availability impact.
A Linux kernel ATM networking flaw that can cause a crash because sigd_send() uses an unvalidated vcc pointer.
Linux kernel ATM networking flaw in sigd_send() caused by an unvalidated VCC pointer, which can lead to a crash.
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.