CVE-2026-64564
sctp: don't free the ASCONF's own transport in DEL-IP processing
Description
In the Linux kernel, the following vulnerability has been resolved: sctp: don't free the ASCONF's own transport in DEL-IP processing sctp_process_asconf() caches the transport the ASCONF chunk is processed against in asconf->transport (== chunk->transport, set once in sctp_rcv()). For an ASCONF located through its Address Parameter by __sctp_rcv_asconf_lookup(), that cached transport corresponds to the Address Parameter, which need not be the packet's source address. sctp_process_asconf_param() rejects a DEL-IP for the packet source address (ADDIP D8, SCTP_ERROR_DEL_SRC_IP), but nothing protects asconf->transport. A single ASCONF can therefore carry, in order: [Address Parameter L] [DEL-IP L] [DEL-IP 0.0.0.0] where L differs from the source. The DEL-IP for L passes the D8 check and calls sctp_assoc_rm_peer() on the transport that asconf->transport still points at, freeing it (RCU-deferred). The following wildcard DEL-IP then reuses the now-dangling asconf->transport in sctp_assoc_set_primary() and sctp_assoc_del_nonprimary_peers(): set_primary() dereferences the freed transport (->ipaddr, ->state) and plants the dangling pointer into asoc->peer.primary_path / active_path, and del_nonprimary_peers(), keeping only the pointer that is no longer on the list, removes every real transport, leaving the association with a transport_count of 0 and primary_path/active_path pointing at freed memory. Reject a DEL-IP that targets the transport the ASCONF is being processed against, mirroring the existing source-address guard, so the wildcard branch can never reuse a freed transport.
In plain language
AI Act nowThis is a critical flaw in the linux kernel: if your systems accept SCTP network traffic, act urgently because a remote attacker can crash or potentially take control of the service.
Unauthenticated network attack against SCTP ASCONF DEL-IP processing can create a use-after-free condition, causing service disruption or potential code execution.
What to do now
- Check whether your linux kernel systems use SCTP or accept SCTP traffic from untrusted networks.
- Ask your operating-system provider for a kernel update that includes the fix for CVE-2026-64564.
- Deploy a kernel containing the applicable fix commit: a9ce31be4cb1a5dd82b3e0a1d0c3e7cbdcd31293, a63afa1f9b12d5293cbe0b77fd45dc0632533a13, 2b324ba3494ae958cba16a453e3e71489b4de7fc, fedeb4468987bcaff85fe3061de5ae052d414740, 74e8f3e7114f0e26d1b2c4c048044db9fcc27603, 85aca407c560aba81b5ce9d3d6cf94c74077d19b, d136b29bf91dd8e3161281b87de597b7311d9462, or 9b2854f86f0b56e9027d68e7a3fc909d1a9b566f.
- Until updated, block inbound SCTP traffic from untrusted networks where that will not disrupt required services.
- Restart into the updated kernel and confirm the running kernel is the vendor-provided fixed build.
CVSS Vector Breakdown
AV:NAttack VectorAC:LAttack ComplexityPR:NPrivileges RequiredUI:NUser InteractionS:UScopeC:HConfidentialityI:HIntegrityA:HAvailabilityAffected Products
Exploitability
References
- Уязвимость SCTPhantom существовала в коде Linux 18 летru-ru·Хакер (xakep.ru)· PoC Linux Kernel privilege-escalation
- ⚡ Weekly Recap: AI Goes Rogue, Metabase 0-Day, MCP Supply-Chain Attacks, and Router Backdoorsen·The Hacker News· Exploited Mythos 5 UNC6671
- 18-Year-Old Linux SCTP Flaw Could Let Local Users Gain Root and Escape Containersen·The Hacker News· Research Linux Kernel privilege-escalation
Unlock Complete Vulnerability Intelligence
Get the full picture for CVE-2026-64564 and every CVE in our database. Create a free account — no credit card required.
Create Free Account