# CVE-2021-46999: linux: In the Linux kernel, the following vulnerability has been resolved:  sctp: do asoc update earlier in sctp_sf_do_dupco...

CVE-2021-46999 is fixed in linux on 1 platform, first by DEBIAN-CVE-2021-46999, released February 28, 2024. It is not reported as exploited. Patch Radar priority: High.

- Web page: https://patchblox.com/security/cve/CVE-2021-46999
- Priority: High
- CVSS: 7.8 (high)
- EPSS: 0.0074
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Feb 28, 2024

## Description

In the Linux kernel, the following vulnerability has been resolved:  sctp: do asoc update earlier in sctp_sf_do_dupcook_a  There's a panic that occurs in a few of envs, the call trace is as below:    [] general protection fault, ... 0x29acd70f1000a: 0000 [#1] SMP PTI   [] RIP: 0010:sctp_ulpevent_notify_peer_addr_change+0x4b/0x1fa [sctp]   []  sctp_assoc_control_transport+0x1b9/0x210 [sctp]   []  sctp_do_8_2_transport_strike.isra.16+0x15c/0x220 [sctp]   []  sctp_cmd_interpreter.isra.21+0x1231/0x1a10 [sctp]   []  sctp_do_sm+0xc3/0x2a0 [sctp]   []  sctp_generate_timeout_event+0x81/0xf0 [sctp]  This is caused by a transport use-after-free issue. When processing a duplicate COOKIE-ECHO chunk in sctp_sf_do_dupcook_a(), both COOKIE-ACK and SHUTDOWN chunks are allocated with the transort from the new asoc. However, later in the sideeffect machine, the old asoc is used to send them out and old asoc's shutdown_last_sent_to is set to the transport that SHUTDOWN chunk attached to in sctp_cmd_setup_t2(), which actually belongs to the new asoc. After the new_asoc is freed and the old asoc T2 timeout, the old asoc's shutdown_last_sent_to that is already freed would be accessed in sctp_sf_t2_timer_expire().  Thanks Alexander and Jere for helping dig into this issue.  To fix it, this patch is to do the asoc update first, then allocate the COOKIE-ACK and SHUTDOWN chunks with the 'updated' old asoc. This would make more sense, as a chunk from an asoc shouldn't be sent out with another asoc. We had fixed quite a few issues caused by this.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 12.15 (bookworm) | 5.10.38-1 | [DEBIAN-CVE-2021-46999](https://patchblox.com/security/data/fix/linux/debian-cve-2021-46999.md) | Feb 28, 2024 |
| Linux | linux Debian 13.5 (trixie) | 5.10.38-1 | [DEBIAN-CVE-2021-46999](https://patchblox.com/security/data/fix/linux/debian-cve-2021-46999.md) | Feb 28, 2024 |
| Linux | linux Debian 14 | 5.10.38-1 | [DEBIAN-CVE-2021-46999](https://patchblox.com/security/data/fix/linux/debian-cve-2021-46999.md) | Feb 28, 2024 |

---

Data as of 2026-11-09T19:38:12Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.