Answer in brief
CVE-2026-64564 records a Unknown severity vulnerability in sctp: don't free the ASCONF's own transport in DEL-IP processing. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-64564 records a Unknown severity vulnerability in sctp: don't free the ASCONF's own transport in DEL-IP processing. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=42e30bf3463cd37d73839376662cb79b4d5c416c <fedeb4468987bcaff85fe3061de5ae052d414740 || >=42e30bf3463cd37d73839376662cb79b4d5c416c <74e8f3e7114f0e26d1b2c4c048044db9fcc27603 || >=42e30bf3463cd37d73839376662cb79b4d5c416c <85aca407c560aba81b5ce9d3d6cf94c74077d19b || >=42e30bf3463cd37d73839376662cb79b4d5c416c <d136b29bf91dd8e3161281b87de597b7311d9462 || >=42e30bf3463cd37d73839376662cb79b4d5c416c <9b2854f86f0b56e9027d68e7a3fc909d1a9b566f | fedeb4468987bcaff85fe3061de5ae052d414740, 74e8f3e7114f0e26d1b2c4c048044db9fcc27603, 85aca407c560aba81b5ce9d3d6cf94c74077d19b, d136b29bf91dd8e3161281b87de597b7311d9462, 9b2854f86f0b56e9027d68e7a3fc909d1a9b566f |
| Linux/Linuxgeneric | 2.6.25 | Not reported |
Published upstream
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=42e30bf3463cd37d73839376662cb79b4d5c416c <fedeb4468987bcaff85fe3061de5ae052d414740 || >=42e30bf3463cd37d73839376662cb79b4d5c416c <74e8f3e7114f0e26d1b2c4c048044db9fcc27603 || >=42e30bf3463cd37d73839376662cb79b4d5c416c <85aca407c560aba81b5ce9d3d6cf94c74077d19b || >=42e30bf3463cd37d73839376662cb79b4d5c416c <d136b29bf91dd8e3161281b87de597b7311d9462 || >=42e30bf3463cd37d73839376662cb79b4d5c416c <9b2854f86f0b56e9027d68e7a3fc909d1a9b566f | fedeb4468987bcaff85fe3061de5ae052d414740, 74e8f3e7114f0e26d1b2c4c048044db9fcc27603, 85aca407c560aba81b5ce9d3d6cf94c74077d19b, d136b29bf91dd8e3161281b87de597b7311d9462, 9b2854f86f0b56e9027d68e7a3fc909d1a9b566f |
| Linux/Linuxgeneric | 2.6.25 | Not reported |
Published upstream
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.