CVE-2021-46999: Vulnerability in Linux Linux
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.
AI Analysis
Technical Summary
CVE-2021-46999 is a vulnerability in the Linux kernel's SCTP (Stream Control Transmission Protocol) implementation. The issue arises from a use-after-free bug related to the handling of duplicate COOKIE-ECHO chunks during SCTP association updates. Specifically, when processing a duplicate COOKIE-ECHO chunk in the function sctp_sf_do_dupcook_a(), both COOKIE-ACK and SHUTDOWN chunks are allocated using the transport from the new association (new_asoc). However, later in the state machine, the old association (old_asoc) is used to send these chunks, and the old_asoc's shutdown_last_sent_to pointer is set to the transport associated with the SHUTDOWN chunk, which actually belongs to the new_asoc. After the new_asoc is freed and the old_asoc's T2 timer expires, the old_asoc's shutdown_last_sent_to pointer, which now points to freed memory, is accessed in sctp_sf_t2_timer_expire(). This results in a use-after-free condition that can cause a kernel panic or general protection fault, leading to a denial of service (DoS). The fix involves updating the association earlier in the processing flow so that the COOKIE-ACK and SHUTDOWN chunks are allocated with the updated old_asoc, ensuring chunks are not sent from one association while being allocated from another. This correction prevents the use-after-free scenario and stabilizes SCTP association handling. The vulnerability affects multiple Linux kernel versions identified by specific commit hashes and was publicly disclosed in February 2024. There are no known exploits in the wild at this time, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to systems running Linux kernels with SCTP enabled, which is commonly used in telecommunications, signaling, and certain enterprise network environments. Exploitation can lead to kernel panics and system crashes, resulting in denial of service conditions. This can disrupt critical infrastructure, especially in telecom operators, financial institutions, and data centers relying on Linux-based systems for high availability. The impact on confidentiality and integrity is limited since the vulnerability is a use-after-free leading to crashes rather than arbitrary code execution. However, availability impact can be significant if exploited on production servers or network devices. Given the widespread use of Linux in European IT infrastructure, especially in cloud services and telecom sectors, this vulnerability could cause operational disruptions if not patched promptly. The lack of known exploits suggests limited immediate threat, but the complexity of the bug and its kernel-level nature means that sophisticated attackers or accidental triggers could cause outages.
Mitigation Recommendations
European organizations should prioritize updating their Linux kernels to versions that include the patch fixing CVE-2021-46999. Since the vulnerability involves SCTP, organizations should audit their environments to identify systems with SCTP enabled and assess their exposure. If SCTP is not required, disabling the SCTP kernel module can reduce the attack surface. For systems where SCTP is critical, ensure kernel updates are applied promptly. Additionally, monitoring kernel logs for signs of general protection faults or panics related to SCTP can help detect attempted exploitation or instability. Network segmentation and limiting exposure of SCTP ports to untrusted networks can further reduce risk. Organizations should also test patches in staging environments to avoid unexpected disruptions. Given the complexity of the issue, collaboration with Linux distribution vendors and telecom equipment providers is recommended to ensure comprehensive remediation.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain, Poland
CVE-2021-46999: Vulnerability in Linux Linux
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.
AI-Powered Analysis
Technical Analysis
CVE-2021-46999 is a vulnerability in the Linux kernel's SCTP (Stream Control Transmission Protocol) implementation. The issue arises from a use-after-free bug related to the handling of duplicate COOKIE-ECHO chunks during SCTP association updates. Specifically, when processing a duplicate COOKIE-ECHO chunk in the function sctp_sf_do_dupcook_a(), both COOKIE-ACK and SHUTDOWN chunks are allocated using the transport from the new association (new_asoc). However, later in the state machine, the old association (old_asoc) is used to send these chunks, and the old_asoc's shutdown_last_sent_to pointer is set to the transport associated with the SHUTDOWN chunk, which actually belongs to the new_asoc. After the new_asoc is freed and the old_asoc's T2 timer expires, the old_asoc's shutdown_last_sent_to pointer, which now points to freed memory, is accessed in sctp_sf_t2_timer_expire(). This results in a use-after-free condition that can cause a kernel panic or general protection fault, leading to a denial of service (DoS). The fix involves updating the association earlier in the processing flow so that the COOKIE-ACK and SHUTDOWN chunks are allocated with the updated old_asoc, ensuring chunks are not sent from one association while being allocated from another. This correction prevents the use-after-free scenario and stabilizes SCTP association handling. The vulnerability affects multiple Linux kernel versions identified by specific commit hashes and was publicly disclosed in February 2024. There are no known exploits in the wild at this time, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to systems running Linux kernels with SCTP enabled, which is commonly used in telecommunications, signaling, and certain enterprise network environments. Exploitation can lead to kernel panics and system crashes, resulting in denial of service conditions. This can disrupt critical infrastructure, especially in telecom operators, financial institutions, and data centers relying on Linux-based systems for high availability. The impact on confidentiality and integrity is limited since the vulnerability is a use-after-free leading to crashes rather than arbitrary code execution. However, availability impact can be significant if exploited on production servers or network devices. Given the widespread use of Linux in European IT infrastructure, especially in cloud services and telecom sectors, this vulnerability could cause operational disruptions if not patched promptly. The lack of known exploits suggests limited immediate threat, but the complexity of the bug and its kernel-level nature means that sophisticated attackers or accidental triggers could cause outages.
Mitigation Recommendations
European organizations should prioritize updating their Linux kernels to versions that include the patch fixing CVE-2021-46999. Since the vulnerability involves SCTP, organizations should audit their environments to identify systems with SCTP enabled and assess their exposure. If SCTP is not required, disabling the SCTP kernel module can reduce the attack surface. For systems where SCTP is critical, ensure kernel updates are applied promptly. Additionally, monitoring kernel logs for signs of general protection faults or panics related to SCTP can help detect attempted exploitation or instability. Network segmentation and limiting exposure of SCTP ports to untrusted networks can further reduce risk. Organizations should also test patches in staging environments to avoid unexpected disruptions. Given the complexity of the issue, collaboration with Linux distribution vendors and telecom equipment providers is recommended to ensure comprehensive remediation.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-02-27T18:42:55.950Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9821c4522896dcbddfed
Added to database: 5/21/2025, 9:08:49 AM
Last enriched: 6/28/2025, 4:41:26 AM
Last updated: 8/6/2025, 12:36:57 AM
Views: 16
Related Threats
CVE-2025-49456: CWE-426 Untrusted Search Path in Zoom Communications Inc Zoom Clients for Windows
MediumCVE-2025-49457: CWE-426 Untrusted Search Path in Zoom Communications Inc Zoom Clients for Windows
CriticalCVE-2025-54238: Out-of-bounds Read (CWE-125) in Adobe Dimension
MediumCVE-2025-8395
LowCVE-2025-54233: Out-of-bounds Read (CWE-125) in Adobe Adobe Framemaker
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.