CVE-2026-64564Linux Linux Kernel Use After Free
NVDCVSS scored by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Vulnerability Summary
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.
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.
CVSS v3.1 Base Metrics — Score 9.8 (CRITICAL)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAttack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
Affected & Patched Versions
- Linux Linux Kernel >= 2.6.25 and < 5.10.265
- Linux Linux Kernel >= 5.11 and < 5.15.216
- Linux Linux Kernel >= 5.16 and < 6.1.183
- Linux Linux Kernel >= 6.2 and < 6.6.148
- Linux Linux Kernel >= 6.7 and < 6.12.101
- Linux Linux Kernel >= 6.13 and < 6.18.42
- Linux Linux Kernel >= 6.19 and < 7.1.6
- Linux Linux Kernel
- Linux Linux Kernel 5.10.265
- Linux Linux Kernel 5.15.216
- Linux Linux Kernel 6.1.183
- Linux Linux Kernel 6.6.148
- Linux Linux Kernel 6.12.101
- Linux Linux Kernel 6.18.42
- Linux Linux Kernel 7.1.6
What to do
Prioritize this fix. Exploit code is public, so attacks can follow quickly.
- Check whether you run Linux Linux Kernel and which version.
- Update to a patched version listed above, then confirm the new version.
- Review logs and exposed services for signs of earlier compromise.
Timeline
- Aug 4, 2026Published
- Nov 12, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new Linux Linux Kernel CVEsYou are reading CVE-2026-64564. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsRelated Coverage
External References
- Patchhttps://git.kernel.org/stable/c/2b324ba3494ae958cba16a453e3e71489b4de7fc
- Patchhttps://git.kernel.org/stable/c/74e8f3e7114f0e26d1b2c4c048044db9fcc27603
- Patchhttps://git.kernel.org/stable/c/85aca407c560aba81b5ce9d3d6cf94c74077d19b
- Patchhttps://git.kernel.org/stable/c/9b2854f86f0b56e9027d68e7a3fc909d1a9b566f
- Patchhttps://git.kernel.org/stable/c/a63afa1f9b12d5293cbe0b77fd45dc0632533a13
- Patchhttps://git.kernel.org/stable/c/a9ce31be4cb1a5dd82b3e0a1d0c3e7cbdcd31293
- Patchhttps://git.kernel.org/stable/c/d136b29bf91dd8e3161281b87de597b7311d9462
- Patchhttps://git.kernel.org/stable/c/fedeb4468987bcaff85fe3061de5ae052d414740
- Exploithttps://matrix.tencent.com/en/2026/08/06/sctphantom-CVE-2026-64564
- Advisoryhttp://www.openwall.com/lists/oss-security/2026/08/06/13
- Advisoryhttp://www.openwall.com/lists/oss-security/2026/08/06/3
- Advisoryhttp://www.openwall.com/lists/oss-security/2026/08/06/4
- Advisoryhttp://www.openwall.com/lists/oss-security/2026/08/07/1
- Advisoryhttp://www.openwall.com/lists/oss-security/2026/08/07/2
- Advisoryhttp://www.openwall.com/lists/oss-security/2026/08/07/8
Data last checked: Nov 18, 2026 23:14 UTC