sctp: don't free the ASCONF's own transport in DEL-IP processing
Summary
| CVE | CVE-2026-64564 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-04 07:16:31 UTC |
| Updated | 2026-08-04 07:16:31 UTC |
| 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 42e30bf3463cd37d73839376662cb79b4d5c416c fedeb4468987bcaff85fe3061de5ae052d414740 git |
Not specified |
| CNA |
Linux |
Linux |
affected 42e30bf3463cd37d73839376662cb79b4d5c416c 74e8f3e7114f0e26d1b2c4c048044db9fcc27603 git |
Not specified |
| CNA |
Linux |
Linux |
affected 42e30bf3463cd37d73839376662cb79b4d5c416c 85aca407c560aba81b5ce9d3d6cf94c74077d19b git |
Not specified |
| CNA |
Linux |
Linux |
affected 42e30bf3463cd37d73839376662cb79b4d5c416c d136b29bf91dd8e3161281b87de597b7311d9462 git |
Not specified |
| CNA |
Linux |
Linux |
affected 42e30bf3463cd37d73839376662cb79b4d5c416c 9b2854f86f0b56e9027d68e7a3fc909d1a9b566f git |
Not specified |
| CNA |
Linux |
Linux |
affected 2.6.25 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 2.6.25 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.148 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.101 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.42 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1.6 7.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2-rc5 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/85aca407c560aba81b5ce9d3d6cf94c74077d19b |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/fedeb4468987bcaff85fe3061de5ae052d414740 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/74e8f3e7114f0e26d1b2c4c048044db9fcc27603 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/d136b29bf91dd8e3161281b87de597b7311d9462 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/9b2854f86f0b56e9027d68e7a3fc909d1a9b566f |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.