Technical impact
In the Linux kernel SCTP implementation, a null pointer dereference occurs when a socket lock is released while waiting for an association to establish. The code path frees extension objects for streams that the peer has removed, yet later send operations resume on the same stream and dereference the now–null extension. This results in a kernel panic, effectively taking the host offline. The bug is a Root Cause: Null Pointer Dereference (CWE-476).
Affected Systems
All Linux kernels that enable the SCTP protocol and are running a version before the patch commit (e.g., the commit added by 77a63d1b813b08c4e5a948f5e04fbaca6176aa8f, the merge b7ad72414c673ce1fa1f463e807cd4f34f8be9bf, or the patch fd56ac95ec31a05b66e8938debfa847f49c0e993) are affected. This includes all standard Linux distributions that ship an unpatched kernel with SCTP support.
Risk and Exploitability
The EPSS score is less than 1% and the vulnerability is not listed in the CISA KEV catalog, but the mechanism leads directly to a kernel panic, a moderate‑to‑high severity event with a CVSS score of 5.5. Based on the description, it is inferred that attackers with network access to a system exposing an SCTP socket can trigger the flaw by sending crafted SCTP packets. The risk is high because the event results in loss of service and potential loss of data, and the CWE 476 (Null Pointer Dereference) underlines the nature of the bug.
Debian DLA