SCTPhantom is a use-after-free vulnerability in the Linux kernel's SCTP Dynamic Address Reconfiguration handling, specifically in ASCONF DEL-IP processing. During sctp_process_asconf(), the kernel caches the transport associated with the ASCONF chunk in asconf->transport. When an ASCONF is located through its Address Parameter, that cached transport can differ from the packet source address. A crafted ASCONF containing a DEL-IP for a non-source address followed by a wildcard DEL-IP can cause the first operation to remove and free the transport still referenced by asconf->transport, after which subsequent logic reuses the dangling pointer in SCTP association management paths such as sctp_assoc_set_primary() and sctp_assoc_del_nonprimary_peers(). This can dereference freed memory, corrupt association state, and leave primary_path and active_path pointing to freed transport structures. The vulnerable logic dates back to Linux 2.6.25.
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.
9 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.