CVE-2026-99582: sctp: re-point retained control chunks on association migration
In the Linux kernel, the following vulnerability has been resolved:
sctp: re-point retained control chunks on association migration
sctpsockmigrate() transfers DATA chunk ownership but leaves retained control chunks pointing at the old socket. A later retransmission can therefore access the socket after it has been freed.
Extend the migration walk to cover retained control chunks and use sctpcontrolsetownerw() to assign their new owner. Reuse the DATA ownership check so each chunk is processed once per pass, even when it is reachable through multiple lists or retained pointers.
Preserve a control chunk's existing authentication key across migration so its final release can still generate SCTPAUTHFREEKEY when needed.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 3.19 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 4.2 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 4.5 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 4.10 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 4.14 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.3.5-1
Event History
Frequently Asked Questions
What conditions are required for exploitation?
The issue requires SCTP association migration, retained SCTP control chunks that still reference the pre-migration socket, and a later retransmission of one of those chunks after that socket has been freed.
What is the likely impact if the vulnerable path is reached?
A retransmission can access a freed socket because retained control chunks keep the old socket as their owner. This is a use-after-free condition in the Linux kernel SCTP implementation.
Is SCTP authentication relevant to the fix?
Yes. Control chunks can retain an authentication key during migration; the fix preserves that key so final chunk release can generate SCTP_AUTH_FREE_KEY when required.