Answer in brief
CVE-2024-26826 records a Unknown severity vulnerability in mptcp: fix data re-injection from stale subflow. 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.
A CVSS score is not reported in the current record. 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 | >=1e1d9d6f119c55c05e8ea78ed3e49046690abffd <6f95120f898b40d13fd441225ef511307853c9c2 || >=1e1d9d6f119c55c05e8ea78ed3e49046690abffd <6673d9f1c2cd984390550dbdf7d5ae07b20abbf8 || >=1e1d9d6f119c55c05e8ea78ed3e49046690abffd <b609c783c535493aa3fca22c7e40a120370b1ca5 || >=1e1d9d6f119c55c05e8ea78ed3e49046690abffd <624902eab7abcb8731b333ec73f206d38d839cd8 || >=1e1d9d6f119c55c05e8ea78ed3e49046690abffd <b6c620dc43ccb4e802894e54b651cf81495e9598 | 6f95120f898b40d13fd441225ef511307853c9c2, 6673d9f1c2cd984390550dbdf7d5ae07b20abbf8, b609c783c535493aa3fca22c7e40a120370b1ca5, 624902eab7abcb8731b333ec73f206d38d839cd8, b6c620dc43ccb4e802894e54b651cf81495e9598 |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
Apr 17, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: mptcp: fix data re-injection from stale subflow When the MPTCP PM detects that a subflow is stale, all the packet scheduler must re-inject all the mptcp-level unacked data. To avoid acquiring unneeded locks, it first try to check if any unacked data is present at all in the RTX queue, but such check is currently broken, as it uses TCP-specific helper on an MPTCP socket. Funnily enough fuzzers and static checkers are happy, as the accessed memory still belongs to the mptcp_sock struct, and even from a functional perspective the recovery completed successfully, as the short-cut test always failed. A recent unrelated TCP change - commit d5fed5addb2b ("tcp: reorganize tcp_sock fast path variables") - exposed the issue, as the tcp field reorganization makes the mptcp code always skip the re-inection. Fix the issue dropping the bogus call: we are on a slow path, the early optimization proved once again to be evil.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-26826 records a Unknown severity vulnerability in mptcp: fix data re-injection from stale subflow. 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.
A CVSS score is not reported in the current record. 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 | >=1e1d9d6f119c55c05e8ea78ed3e49046690abffd <6f95120f898b40d13fd441225ef511307853c9c2 || >=1e1d9d6f119c55c05e8ea78ed3e49046690abffd <6673d9f1c2cd984390550dbdf7d5ae07b20abbf8 || >=1e1d9d6f119c55c05e8ea78ed3e49046690abffd <b609c783c535493aa3fca22c7e40a120370b1ca5 || >=1e1d9d6f119c55c05e8ea78ed3e49046690abffd <624902eab7abcb8731b333ec73f206d38d839cd8 || >=1e1d9d6f119c55c05e8ea78ed3e49046690abffd <b6c620dc43ccb4e802894e54b651cf81495e9598 | 6f95120f898b40d13fd441225ef511307853c9c2, 6673d9f1c2cd984390550dbdf7d5ae07b20abbf8, b609c783c535493aa3fca22c7e40a120370b1ca5, 624902eab7abcb8731b333ec73f206d38d839cd8, b6c620dc43ccb4e802894e54b651cf81495e9598 |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
Apr 17, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: mptcp: fix data re-injection from stale subflow When the MPTCP PM detects that a subflow is stale, all the packet scheduler must re-inject all the mptcp-level unacked data. To avoid acquiring unneeded locks, it first try to check if any unacked data is present at all in the RTX queue, but such check is currently broken, as it uses TCP-specific helper on an MPTCP socket. Funnily enough fuzzers and static checkers are happy, as the accessed memory still belongs to the mptcp_sock struct, and even from a functional perspective the recovery completed successfully, as the short-cut test always failed. A recent unrelated TCP change - commit d5fed5addb2b ("tcp: reorganize tcp_sock fast path variables") - exposed the issue, as the tcp field reorganization makes the mptcp code always skip the re-inection. Fix the issue dropping the bogus call: we are on a slow path, the early optimization proved once again to be evil.
Quoted source text, attributed separately from HOL analysis.