0.0
NA
CVE-2026-98614
sctp: avoid livelock while updating retransmit path
Description

In the Linux kernel, the following vulnerability has been resolved: sctp: avoid livelock while updating retransmit path sctp_assoc_update_retran_path() can loop forever when every remaining transport, including retran_path, is SCTP_UNCONFIRMED: the state check runs before the wraparound test, so the loop cannot observe that it has completed a full pass. Fix this by considering a transport only when it is not UNCONFIRMED, then checking whether the walk has returned to retran_path. This makes the full-pass termination independent of the transport state while preserving the existing fallback selection semantics. Also restore the NULL guard around the retran_path assignment. In the all-UNCONFIRMED case there is no eligible replacement transport, and installing NULL would leave later retransmit-path users and the debug print with a NULL path.

INFO

Published Date :

Oct. 18, 2026, 4:17 p.m.

Last Modified :

Oct. 18, 2026, 4:17 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2026-98614 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
Solution
Update the Linux kernel to prevent infinite loops during retransmission path updates.
  • Update the Linux kernel to the latest version.
  • Apply the patch for sctp livelock vulnerability.
  • Ensure transport states are checked before loop termination.
  • Restore NULL guard around retran_path assignment.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-98614 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-98614 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-98614 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-98614 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Oct. 18, 2026

    Action Type Old Value New Value
    Added Description In the Linux kernel, the following vulnerability has been resolved: sctp: avoid livelock while updating retransmit path sctp_assoc_update_retran_path() can loop forever when every remaining transport, including retran_path, is SCTP_UNCONFIRMED: the state check runs before the wraparound test, so the loop cannot observe that it has completed a full pass. Fix this by considering a transport only when it is not UNCONFIRMED, then checking whether the walk has returned to retran_path. This makes the full-pass termination independent of the transport state while preserving the existing fallback selection semantics. Also restore the NULL guard around the retran_path assignment. In the all-UNCONFIRMED case there is no eligible replacement transport, and installing NULL would leave later retransmit-path users and the debug print with a NULL path.
    Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/98xxx/CVE-2026-98614.json">CVE-2026-98614</a>
    Added Reference https://git.kernel.org/stable/c/173610fff55022a5ad1579fbcc7faa97467b58b7
    Added Reference https://git.kernel.org/stable/c/3fe624c3843694ab096fdb198526ba0c659febbe
    Added Reference https://git.kernel.org/stable/c/43410c1f2db53516e95ddd7e5b4b02f495b78121
    Added Reference https://git.kernel.org/stable/c/83b1a7f9e718828ef364a7b004254ebb2d0035fe
    Added Reference https://git.kernel.org/stable/c/c9338057df1025f578fe7d0ff08bada87b8b838d
    Added Reference https://git.kernel.org/stable/c/d2c31b837406395e576afeb25958c98e9938f3f6
    Added Reference https://git.kernel.org/stable/c/d893a7cc1cb41dd510f338bb2bfd8f29b14eaf49
    Added Reference https://git.kernel.org/stable/c/ddc34cc0834c873871e88b055ee6a260676efe97
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.