Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-98614 Overview
CVE-2026-98614 is a Linux kernel vulnerability in the Stream Control Transmission Protocol (SCTP) subsystem. The flaw resides in sctp_assoc_update_retran_path(), which can enter an infinite loop when every remaining transport in an association, including retran_path, is in the SCTP_UNCONFIRMED state. The function's state check runs before the wraparound test, so the loop never detects that it has completed a full pass through the transport list.
The condition produces a kernel-side livelock that can stall SCTP processing and consume CPU resources. The upstream fix also restores a NULL guard around the retran_path assignment to prevent downstream NULL dereferences when no eligible transport exists.
Critical Impact
A livelock in SCTP retransmit path selection can trigger CPU exhaustion and denial of service on hosts running SCTP workloads such as telecom signaling (Diameter, SIGTRAN) or clustered applications.
Affected Products
- Linux kernel versions containing sctp_assoc_update_retran_path() prior to the referenced stable patches
- Distributions shipping affected mainline and long-term kernels
- Systems with SCTP enabled, including telecom and HA cluster deployments
Discovery Timeline
- 2026-10-18 - CVE-2026-98614 published to the National Vulnerability Database
- 2026-10-19 - Last updated in NVD database
Technical Details for CVE-2026-98614
Vulnerability Analysis
The SCTP association maintains a list of peer transports, each tracked by state (SCTP_ACTIVE, SCTP_INACTIVE, SCTP_UNCONFIRMED). When the stack needs to update the retransmit path, sctp_assoc_update_retran_path() walks the transport list to select a replacement. The walker ordering places the state eligibility check before the test that detects a complete loop back to the original retran_path.
When every transport, including retran_path itself, is SCTP_UNCONFIRMED, no transport satisfies the eligibility check. The wraparound detection never executes, so the loop iterates indefinitely. Execution remains inside the kernel context that triggered the update, blocking the CPU and preventing progress on associated workqueues or softirq handlers.
A secondary issue affects correctness. Earlier variants of the code allowed retran_path to be assigned a NULL value when no eligible transport existed. Subsequent retransmit-path consumers and the SCTP debug print would then operate on a NULL pointer.
Root Cause
The root cause is an ordering defect in the loop termination logic. The state filter gates the wraparound check, so a uniformly ineligible transport set produces an infinite loop. This is a logic flaw [CWE-835-class] rather than a memory safety issue.
Attack Vector
Triggering the condition requires an SCTP association whose transports all transition to SCTP_UNCONFIRMED. A remote peer that can influence heartbeat behavior or path confirmation state on an active SCTP association may be able to drive the local stack into this configuration. Local workloads that programmatically add unconfirmed transports can also reach the condition. The vulnerability does not require authentication at the application layer, but it does require an existing SCTP peering relationship.
No public proof-of-concept has been published, and the CVE is not listed in CISA KEV. Refer to the upstream patches for the exact code paths affected: Kernel Patch 173610f and Kernel Patch d893a7c.
Detection Methods for CVE-2026-98614
Indicators of Compromise
- Sustained 100% CPU utilization pinned to a single kernel thread or softirq context handling SCTP traffic.
- Soft lockup or RCU stall warnings in dmesg referencing SCTP functions, including sctp_assoc_update_retran_path.
- SCTP associations stalling with no retransmissions progressing while all peer transports report UNCONFIRMED.
Detection Strategies
- Monitor kernel logs for watchdog: BUG: soft lockup entries whose stack traces include SCTP symbols.
- Collect perf or ftrace samples on affected hosts to identify time spent inside the SCTP retransmit path selection loop.
- Inventory kernel versions against the fixed commits listed in the upstream references and flag unpatched hosts running SCTP workloads.
Monitoring Recommendations
- Alert on SCTP association transports stuck in the UNCONFIRMED state for extended periods.
- Track per-CPU utilization spikes that correlate with SCTP traffic volume or peer connectivity changes.
- Centralize kernel logs and watchdog events so livelock symptoms can be correlated across a fleet.
How to Mitigate CVE-2026-98614
Immediate Actions Required
- Identify all hosts with the SCTP module loaded by checking lsmod | grep sctp and prioritize them for patching.
- Apply the latest stable kernel update from your distribution that includes the referenced upstream fixes.
- On systems that do not require SCTP, blacklist the sctp kernel module to remove the attack surface entirely.
Patch Information
The fix changes the loop in sctp_assoc_update_retran_path() so a transport is considered only when it is not SCTP_UNCONFIRMED, after which the walker checks whether it has returned to retran_path. This makes full-pass termination independent of transport state. The patch also restores the NULL guard around the retran_path assignment. Stable backports are available in commits 173610f, 3fe624c, 43410c1, 83b1a7f, c9338057, d2c31b8, d893a7c, and ddc34cc.
Workarounds
- Disable or unload the SCTP module on hosts that do not require the protocol: modprobe -r sctp and blacklist via /etc/modprobe.d/.
- Restrict SCTP peering to trusted networks using host firewall rules to limit which peers can influence transport state.
- Monitor association health and automate restart of SCTP-dependent services if soft lockup conditions are detected.
# Blacklist the SCTP module where the protocol is not needed
echo "install sctp /bin/true" | sudo tee /etc/modprobe.d/disable-sctp.conf
sudo modprobe -r sctp
# Verify module is not loaded
lsmod | grep sctp
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

