In the Linux kernel's SCTP implementation, the function used to update the retransmit path can enter an infinite loop when all remaining transports are in an unconfirmed state. The loop condition checks the transport state before verifying if it has returned to the starting point, preventing the walk from terminating. This livelock not only stalls the kernel but also leaves the retransmit path set to NULL, potentially causing a null pointer dereference later when the path is accessed, thereby allowing the kernel to crash. The combination of a perpetual loop and a possible null pointer dereference results in a significant denial‑of‑service vulnerability that can bring affected systems offline.

Any Linux system running the kernel in its default configuration is potentially affected. The specific kernel releases prior to the integration of the fix are not enumerated in the provided data, so users should consult the commit history of the Linux kernel to determine if their version contains the living‑lock repair.

The CVSS score and EPSS are not available, and the vulnerability is not listed in CISA's KEV catalog, so public evidence of exploitation is currently absent. Nevertheless, an attacker could trigger the faulty SCTP path update by sending crafted SCTP traffic, effectively leading to a remote or local denial of service on the target host. Based on the description, the likely attack vector is a network‑based attack that exploits the SCTP stack to induce the livelock or null pointer dereference. The absence of a known exploit mitigates immediate risk only partially, as the flaw can still be triggered by an active adversary with sufficient network access.