Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98614sctp: 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.

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 1 day later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0 – < 3fe624c3843694ab096fdb198526ba0c659febbe
    • affected 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0 – < 43410c1f2db53516e95ddd7e5b4b02f495b78121
    • affected 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0 – < d893a7cc1cb41dd510f338bb2bfd8f29b14eaf49
    • affected 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0 – < 83b1a7f9e718828ef364a7b004254ebb2d0035fe
    • affected 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0 – < 173610fff55022a5ad1579fbcc7faa97467b58b7
    • affected 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0 – < c9338057df1025f578fe7d0ff08bada87b8b838d
    • affected 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0 – < ddc34cc0834c873871e88b055ee6a260676efe97
    • affected 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0 – < d2c31b837406395e576afeb25958c98e9938f3f6
    • affected 8ceaec02b17397d12719a282945abc95f8149d9f
    • affected d2c2bdcdd8c5ce3d2a68aa3353ed1f340c3e500e
    • affected 3.10.106 – < 3.11
    • affected 3.12.71 – < 3.13
  • Linux · Linux

    • affected 3.14
    • unaffected < 3.14
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.55 – ≤ 6.18.*
    • unaffected 7.2.9 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98614 badge
[![CVE-2026-98614](https://cveledger.app/badge/CVE-2026-98614.svg)](https://cveledger.app/cve/CVE-2026-98614)

Record last updated .