CVE-2026-52935

published 24 Jun 2026 · updated 14 Nov 2026

xfrm: espintcp: do not reuse an in-progress partial send

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f9b38a8fbfa07f1deaf7ee1eb38fa8b21ea13990, Kernel 1777ceac4bea5e568a5ad44b7f9bb219c1db21b6, Kernel 37487d55bf3300e3d2c1368da5c2bd3e3834ea4f and 12 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <f9b38a8fbfa07f1deaf7ee1eb38fa8b21ea13990, >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <1777ceac4bea5e568a5ad44b7f9bb219c1db21b6, >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <37487d55bf3300e3d2c1368da5c2bd3e3834ea4f, >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <6564e9c7af7e1dc7bfe7f3093b728abe484d7630, >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <8c6c691bf062dc0753a139a4ab8cb92a70fcf8f3, >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <aa82a078f70f7ff88ba7d1017134e79d1ac140f2, >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <ba21439302db9a82fe4edbed1e38a97271529421, >=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <c381039ade2e161ab08c0eda73c4f8b9a7115928, =5.6f9b38a8fbfa07f1deaf7ee1eb38fa8b21ea13990, 1777ceac4bea5e568a5ad44b7f9bb219c1db21b6, 37487d55bf3300e3d2c1368da5c2bd3e3834ea4f, 6564e9c7af7e1dc7bfe7f3093b728abe484d7630, 8c6c691bf062dc0753a139a4ab8cb92a70fcf8f3, aa82a078f70f7ff88ba7d1017134e79d1ac140f2, ba21439302db9a82fe4edbed1e38a97271529421, c381039ade2e161ab08c0eda73c4f8b9a7115928
linux-kernel: Kernel>=5.16.0 <6.1.176, >=5.6.0 <5.10.259, >=6.13.0 <6.18.36, >=6.19.0 <7.0.13, >=6.2.0 <6.6.143, >=6.7.0 <6.12.94, >=5.11.0 <5.15.2106.1.176, 5.10.259, 6.18.36, 7.0.13, 6.6.143, 6.12.94, 5.15.210

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-52935 severity on Zeptric[![CVE-2026-52935](https://zeptric.io/badge/cve/CVE-2026-52935.svg)](https://zeptric.io/cve/CVE-2026-52935)