Linux kernel use-after-free in SCTP control chunk migration
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
sctp: re-point retained control chunks on association migration
sctp_sock_migrate() 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 sctp_control_set_owner_w() 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 SCTP_AUTH_FREE_KEY when needed.
From the CVE record · Linux
The Linux kernel’s SCTP association migration leaves retained control chunks pointing to the old socket. If that socket is freed, a later retransmission can access it after free. The input does not specify whether authentication or user interaction is required, or how an attacker could trigger the condition.
Engineers running Linux kernels with SCTP support should check their versions against the vendor advisory; affected versions are not specified.