CVE-2026-74586
Description
A flaw was found in the Linux kernel's Stream Control Transmission Protocol (SCTP) implementation. An authenticated remote SCTP peer can trigger a use-after-free vulnerability by adding and then immediately removing a transport within the same ASCONF chunk. This can lead to a system crash, resulting in a denial of service.
Statement
An SCTP use-after-free can occur when an authenticated remote peer sends an ASCONF chunk that adds a new transport and then removes it with a wildcard DEL-IP operation. The removed transport can remain referenced by asoc->new_transport and later be attached to a queued HEARTBEAT without a valid transport reference. After RCU frees the transport, subsequent ASCONF_ACK processing can reach sctp_outq_select_transport() and dereference the freed object. The upstream reproducer reliably triggered a KASAN slab-use-after-free while reading transport->state.
Exploitation requires an existing SCTP association with an authenticated peer capable of ASCONF dynamic address reconfiguration and a specific multi-stage sequence, increasing practical attack complexity. For CVSS, AV:N reflects that the trigger originates from a remote SCTP peer, while PR:L reflects the required authenticated peer context rather than arbitrary unauthenticated network access.
The demonstrated impact is a kernel use-after-free read that can cause a kernel crash and denial of service. Confidentiality or integrity impact is possible as a paranoid worst case because a freed kernel networking object is accessed, but should not be considered confirmed impact.
Mitigation
To mitigate this issue on systems where the SCTP protocol is not needed, prevent the sctp kernel module from loading:
1. Add the module configuration to prevent loading:
# echo "install sctp /bin/true" > /etc/modprobe.d/sctp-disable.conf
2. Unload the module from the active system if loaded:
# modprobe -r sctp
Warning: If the sctp module is currently in use, unloading will fail and a system reboot will be required to apply the changes. Disabling this module will cause any applications requiring SCTP networking functionality to fail.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.5 | N/A | 9.8 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | Low |
| Privileges Required | Low | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
