sctp: drop a chunk if its transport was removed
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: sctp: drop a chunk if its transport was removed sctp_rcv() resolves the transport once per packet and leaves it in chunk->transport. The lookup reference, or the one sctp_add_backlog() takes if the socket is owned by userspace, keeps it around until the chunk has been processed. An authenticated ASCONF DEL-IP can remove it in the meantime. sctp_assoc_rm_peer() takes the transport out of the association and calls sctp_transport_free(), which tags it dead and drops the reference the association held. There is a window on both paths: the packet can sit on the socket backlog, and on the direct path the lookup completes before bh_lock_sock(). The DATA chunk in that packet puts the removed transport back into asoc->peer.last_data_from. Once the packet is done that reference goes away and the transport is freed by RCU, so the next delayed SACK carries the pointer into the SACK chunk and sctp_outq_select_transport() reads the freed transport's state. Drop the chunk in sctp_inq_push(), next to the existing rcvr->dead check. Both paths reach it with the association's socket lock held. The peer retransmits it.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 3fc072e7cb4a0ff251d13cfc2d24f62489cd9386; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in d7cb5ad832095dc4becfdb2a36007ffd50e49fb0; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 0422b092a3d43ca462932ff9f747731ca078d1d4; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 928fd7920ba37cc5637a211b9be979083413a2fa; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in c6c86a5e62a4fec36692ddd64b9144b660f71f96; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 1035bdef1efb9b1076d1a57b81e08c637ff08ecc; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 3537961df2163258bddc230db0e18dc14e925ea6; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 03a9d10ecf71f54b2af8020935f2033d4a132be5
- Linux Linux
2.6.12
- KernelLinux
From 2.6.12 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.109; From 6.13.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4
References 8
git.kernel.org
- stable/c/3fc072e7cb4a0ff251d13cfc2d24f62489cd9386
- stable/c/d7cb5ad832095dc4becfdb2a36007ffd50e49fb0
- stable/c/0422b092a3d43ca462932ff9f747731ca078d1d4
- stable/c/928fd7920ba37cc5637a211b9be979083413a2fa
- stable/c/c6c86a5e62a4fec36692ddd64b9144b660f71f96
- stable/c/1035bdef1efb9b1076d1a57b81e08c637ff08ecc
- stable/c/3537961df2163258bddc230db0e18dc14e925ea6
- stable/c/03a9d10ecf71f54b2af8020935f2033d4a132be5