Answer in brief
CVE-2026-98130 records a High severity (CVSS 8.1) vulnerability in sctp: fix a TOCTOU race in SCTP_CMD_TIMER_START. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=20a785aa52c82246055a089e55df9dac47d67da1 <e42ba56281ca3ae2dcb3558bebee9a1c9a4831d9 || >=20a785aa52c82246055a089e55df9dac47d67da1 <00b841bac10230c557be6b38efc48508198fe23e || >=20a785aa52c82246055a089e55df9dac47d67da1 <3d698d1e6c8bc41e3e1707777a016f1bdd07842d || >=20a785aa52c82246055a089e55df9dac47d67da1 <2188569e7e1b0bc3f3b557dc97ab7a02befc11c8 || 9c0a4652f750afe3b4468cbcd9335b244ce2facd || 70989e501fbce502198d82da88358ce453575a05 || 085bb270b4b1168c93afb37bbafc881207d15443 || >=4.19.126 <4.20 || >=5.4.44 <5.5 || >=5.6.16 <5.7 | e42ba56281ca3ae2dcb3558bebee9a1c9a4831d9, 00b841bac10230c557be6b38efc48508198fe23e, 3d698d1e6c8bc41e3e1707777a016f1bdd07842d, 2188569e7e1b0bc3f3b557dc97ab7a02befc11c8, 4.20, 5.5, 5.7 |
| Linux/Linuxgeneric | 5.7 | Not reported |
Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
In the Linux kernel, the following vulnerability has been resolved: sctp: fix a TOCTOU race in SCTP_CMD_TIMER_START The SCTP_CMD_TIMER_START handler checks timer_pending() before calling timer_reduce(). The timer can expire and detach between these operations, causing timer_reduce() to rearm the timer without taking the association reference required for the newly armed timer. The timer callback later unconditionally drops its association reference, which can leave the association reference count unbalanced and result in use-after-free during association teardown. Use the return value of timer_reduce() to determine whether the timer was actually armed. Take the association reference only when timer_reduce() successfully starts a new timer, closing the race between checking the timer state and rearming it. This issue was reported by Nico Yip (@_cyeaa_) working with TrendAI Zero Day Initiative.
Quoted source text, attributed separately from HOL analysis.