Answer in brief
CVE-2026-97523 records a High severity (CVSS 7.5) vulnerability in mptcp: close race between scheduler and state change. 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 7.5. 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 | >=c886d70286bf3ad411eb3d689328a67f7102c6ae <8f11430d51ff8365bc51b670bc3002b65ae4c6b7 || >=c886d70286bf3ad411eb3d689328a67f7102c6ae <a09c87abf10a0a7e203137c75b5381aa63d9b31d || >=c886d70286bf3ad411eb3d689328a67f7102c6ae <4c856f3c151a2f3fa237caa651c44015916ca584 || >=c886d70286bf3ad411eb3d689328a67f7102c6ae <42064de57fb83231fcc89663a94885f228a1ee53 || fb9c73ef2ac2ec816efdc8b9267bc04e1369c20b || 8caf5c15b5288d52d9c89374d6c10fa32ee84ec5 || >=5.15.190 <5.16 || >=5.19.4 <5.20 | 8f11430d51ff8365bc51b670bc3002b65ae4c6b7, a09c87abf10a0a7e203137c75b5381aa63d9b31d, 4c856f3c151a2f3fa237caa651c44015916ca584, 42064de57fb83231fcc89663a94885f228a1ee53, 5.16, 5.20 |
| Linux/Linuxgeneric | 6.0 | 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: mptcp: close race between scheduler and state change The mptcp scheduler may race with subflow sockets state change: data transmission on the selected socket may fail and a later release could try to use mss_now reset to 0 for a divide operation. Address the issue by explicitly checking for the critical scenario.
Quoted source text, attributed separately from HOL analysis.