CVE-2026-64564

published 4 Aug 2026 · updated 12 Nov 2026

sctp: don't free the ASCONF's own transport in DEL-IP processing

10.0CriticalCVSS 9.8EPSS 1%1 public exploits

A public exploit exists; no exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 5.10.265, Kernel 5.15.216, Kernel 6.1.183 and 12 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=2.6.25 <5.10.265, >=5.11 <5.15.216, >=5.16 <6.1.183, >=6.13 <6.18.42, >=6.19 <7.1.6, >=6.2 <6.6.148, >=6.7 <6.12.101, =7.2, >=42e30bf3463cd37d73839376662cb79b4d5c416c <74e8f3e7114f0e26d1b2c4c048044db9fcc27603, >=42e30bf3463cd37d73839376662cb79b4d5c416c <85aca407c560aba81b5ce9d3d6cf94c74077d19b, >=42e30bf3463cd37d73839376662cb79b4d5c416c <9b2854f86f0b56e9027d68e7a3fc909d1a9b566f, >=42e30bf3463cd37d73839376662cb79b4d5c416c <a63afa1f9b12d5293cbe0b77fd45dc0632533a13, >=42e30bf3463cd37d73839376662cb79b4d5c416c <a9ce31be4cb1a5dd82b3e0a1d0c3e7cbdcd31293, >=42e30bf3463cd37d73839376662cb79b4d5c416c <d136b29bf91dd8e3161281b87de597b7311d9462, >=42e30bf3463cd37d73839376662cb79b4d5c416c <fedeb4468987bcaff85fe3061de5ae052d414740, =2.6.25, >=42e30bf3463cd37d73839376662cb79b4d5c416c <2b324ba3494ae958cba16a453e3e71489b4de7fc5.10.265, 5.15.216, 6.1.183, 6.18.42, 7.1.6, 6.6.148, 6.12.101, 74e8f3e7114f0e26d1b2c4c048044db9fcc27603, 85aca407c560aba81b5ce9d3d6cf94c74077d19b, 9b2854f86f0b56e9027d68e7a3fc909d1a9b566f, a63afa1f9b12d5293cbe0b77fd45dc0632533a13, a9ce31be4cb1a5dd82b3e0a1d0c3e7cbdcd31293, d136b29bf91dd8e3161281b87de597b7311d9462, fedeb4468987bcaff85fe3061de5ae052d414740, 2b324ba3494ae958cba16a453e3e71489b4de7fc
linux-kernel: Kernel>=2.6.25 <5.10.265, >=5.11.0 <5.15.216, >=5.16.0 <6.1.183, >=6.13.0 <6.18.42, >=6.19.0 <7.1.6, >=6.2.0 <6.6.148, >=6.7.0 <6.12.1015.10.265, 5.15.216, 6.1.183, 6.18.42, 7.1.6, 6.6.148, 6.12.101

Exploit evidence

1 public sources

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-64564 severity on Zeptric[![CVE-2026-64564](https://zeptric.io/badge/cve/CVE-2026-64564.svg)](https://zeptric.io/cve/CVE-2026-64564)