CVE-2026-98614: sctp: avoid livelock while updating retransmit path
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 173610fff55022a5ad1579fbcc7faa97467b58b7, 3.11, 3.13; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 173610fff55022a5ad1579fbcc7faa97467b58b7, 3.11, 3.13; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 18, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 8ceaec02b17397d12719a282945abc95f8149d9f, d2c2bdcdd8c5ce3d2a68aa3353ed1f340c3e500e, 3.14affected
- 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0 and later · before 3fe624c3843694ab096fdb198526ba0c659febbeaffected · git
- 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0 and later · before 43410c1f2db53516e95ddd7e5b4b02f495b78121affected · git
- 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0 and later · before d893a7cc1cb41dd510f338bb2bfd8f29b14eaf49affected · git
- 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0 and later · before 83b1a7f9e718828ef364a7b004254ebb2d0035feaffected · git
- 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0 and later · before 173610fff55022a5ad1579fbcc7faa97467b58b7affected · git
- 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0 and later · before c9338057df1025f578fe7d0ff08bada87b8b838daffected · git
- 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0 and later · before ddc34cc0834c873871e88b055ee6a260676efe97affected · git
- 4c47af4d5eb2c2f78f886079a3920a7078a6f0a0 and later · before d2c31b837406395e576afeb25958c98e9938f3f6affected · git
- 3.10.106 and later · before 3.11affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.9-1 | 7.2.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98612Oct 18, 2026 · net: usb: catc: bound the RX packet length in catc_rx_done()0Monitor
- ← EarlierCVE-2026-98613Oct 18, 2026 · bpf: Bound ownership depth through local kptrs and graph roots0Monitor
- Later →CVE-2026-98615Oct 18, 2026 · eth: fbnic: Set AW_FLUSH_MODE alongside AW_FLUSH when flushing the mailbox0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 173610fff55022a5ad1579fbcc7faa97467b58b7 | Vendor (CNA) |
| Linux Linux | 3.11 | Vendor (CNA) |
| Linux Linux | 3.13 | Vendor (CNA) |
| Linux Linux | 3fe624c3843694ab096fdb198526ba0c659febbe | Vendor (CNA) |
| Linux Linux | 43410c1f2db53516e95ddd7e5b4b02f495b78121 | Vendor (CNA) |
| Linux Linux | 83b1a7f9e718828ef364a7b004254ebb2d0035fe | Vendor (CNA) |
| Linux Linux | c9338057df1025f578fe7d0ff08bada87b8b838d | Vendor (CNA) |
| Linux Linux | d2c31b837406395e576afeb25958c98e9938f3f6 | Vendor (CNA) |
| Linux Linux | d893a7cc1cb41dd510f338bb2bfd8f29b14eaf49 | Vendor (CNA) |
| Linux Linux | ddc34cc0834c873871e88b055ee6a260676efe97 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.159.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 7, 2026+20 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1351 · Oct 19, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/3fe624c3843694ab096fdb198526ba0c659febbe
- git.kernel.org/stable/c/43410c1f2db53516e95ddd7e5b4b02f495b78121
- git.kernel.org/stable/c/83b1a7f9e718828ef364a7b004254ebb2d0035fe
- git.kernel.org/stable/c/c9338057df1025f578fe7d0ff08bada87b8b838d
- git.kernel.org/stable/c/d2c31b837406395e576afeb25958c98e9938f3f6
- git.kernel.org/stable/c/d893a7cc1cb41dd510f338bb2bfd8f29b14eaf49
- git.kernel.org/stable/c/ddc34cc0834c873871e88b055ee6a260676efe97
Vendor advisories and official records. Exploit/PoC links are deliberately left out.