Answer in brief
CVE-2026-52935 records a High severity (CVSS 7.8) vulnerability in xfrm: espintcp: do not reuse an in-progress partial send. 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.
Answer in brief
CVE-2026-52935 records a High severity (CVSS 7.8) vulnerability in xfrm: espintcp: do not reuse an in-progress partial send. 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.8. 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 | >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <6564e9c7af7e1dc7bfe7f3093b728abe484d7630 || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <1777ceac4bea5e568a5ad44b7f9bb219c1db21b6 || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <8c6c691bf062dc0753a139a4ab8cb92a70fcf8f3 || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <aa82a078f70f7ff88ba7d1017134e79d1ac140f2 || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <ba21439302db9a82fe4edbed1e38a97271529421 || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <f9b38a8fbfa07f1deaf7ee1eb38fa8b21ea13990 || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <37487d55bf3300e3d2c1368da5c2bd3e3834ea4f || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <c381039ade2e161ab08c0eda73c4f8b9a7115928 | 6564e9c7af7e1dc7bfe7f3093b728abe484d7630, 1777ceac4bea5e568a5ad44b7f9bb219c1db21b6, 8c6c691bf062dc0753a139a4ab8cb92a70fcf8f3, aa82a078f70f7ff88ba7d1017134e79d1ac140f2, ba21439302db9a82fe4edbed1e38a97271529421, f9b38a8fbfa07f1deaf7ee1eb38fa8b21ea13990, 37487d55bf3300e3d2c1368da5c2bd3e3834ea4f, c381039ade2e161ab08c0eda73c4f8b9a7115928 |
| Linux/Linuxgeneric | 5.6 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
In the Linux kernel, the following vulnerability has been resolved: xfrm: espintcp: do not reuse an in-progress partial send espintcp keeps a single in-flight transmit in ctx->partial. Before building a new sk_msg, espintcp_sendmsg() first tries to flush that state through espintcp_push_msgs(). For blocking callers, espintcp_push_msgs() may return success even when the previous partial send is still pending. espintcp_sendmsg() would then reinitialize emsg->skmsg and reuse ctx->partial while the old transfer still owns that state. Do not rebuild the send message when ctx->partial is still in progress. If espintcp_push_msgs() returns with emsg->len still set, fail the new send instead of overwriting the live partial state. This is a memory-safety fix: reusing the live partial-send state can leave a stale offset attached to a new sk_msg and lead to an out-of- bounds read in the send path. tcp_sendmsg_locked() already handles waiting for send buffer memory, so the fix here is just to preserve espintcp's one-message-at-a-time transmit state.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. 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 | >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <6564e9c7af7e1dc7bfe7f3093b728abe484d7630 || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <1777ceac4bea5e568a5ad44b7f9bb219c1db21b6 || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <8c6c691bf062dc0753a139a4ab8cb92a70fcf8f3 || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <aa82a078f70f7ff88ba7d1017134e79d1ac140f2 || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <ba21439302db9a82fe4edbed1e38a97271529421 || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <f9b38a8fbfa07f1deaf7ee1eb38fa8b21ea13990 || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <37487d55bf3300e3d2c1368da5c2bd3e3834ea4f || >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <c381039ade2e161ab08c0eda73c4f8b9a7115928 | 6564e9c7af7e1dc7bfe7f3093b728abe484d7630, 1777ceac4bea5e568a5ad44b7f9bb219c1db21b6, 8c6c691bf062dc0753a139a4ab8cb92a70fcf8f3, aa82a078f70f7ff88ba7d1017134e79d1ac140f2, ba21439302db9a82fe4edbed1e38a97271529421, f9b38a8fbfa07f1deaf7ee1eb38fa8b21ea13990, 37487d55bf3300e3d2c1368da5c2bd3e3834ea4f, c381039ade2e161ab08c0eda73c4f8b9a7115928 |
| Linux/Linuxgeneric | 5.6 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
In the Linux kernel, the following vulnerability has been resolved: xfrm: espintcp: do not reuse an in-progress partial send espintcp keeps a single in-flight transmit in ctx->partial. Before building a new sk_msg, espintcp_sendmsg() first tries to flush that state through espintcp_push_msgs(). For blocking callers, espintcp_push_msgs() may return success even when the previous partial send is still pending. espintcp_sendmsg() would then reinitialize emsg->skmsg and reuse ctx->partial while the old transfer still owns that state. Do not rebuild the send message when ctx->partial is still in progress. If espintcp_push_msgs() returns with emsg->len still set, fail the new send instead of overwriting the live partial state. This is a memory-safety fix: reusing the live partial-send state can leave a stale offset attached to a new sk_msg and lead to an out-of- bounds read in the send path. tcp_sendmsg_locked() already handles waiting for send buffer memory, so the fix here is just to preserve espintcp's one-message-at-a-time transmit state.
Quoted source text, attributed separately from HOL analysis.