High 7.8Published Jun 24, 2026

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

Updated under an hour ago (Oct 27, 2026, 9:00 AM ET)

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

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.

CVSS: 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE): CWE-362
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Modified
Record last updated: Oct 19, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	from e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 before 6564e9c7af7e1dc7bfe7f3093b728abe484d7630; from e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 before 1777ceac4bea5e568a5ad44b7f9bb219c1db21b6; from e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 before 8c6c691bf062dc0753a139a4ab8cb92a70fcf8f3; from e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 before aa82a078f70f7ff88ba7d1017134e79d1ac140f2; from e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 before ba21439302db9a82fe4edbed1e38a97271529421; from e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 before f9b38a8fbfa07f1deaf7ee1eb38fa8b21ea13990; from e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 before 37487d55bf3300e3d2c1368da5c2bd3e3834ea4f; from e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 before c381039ade2e161ab08c0eda73c4f8b9a7115928	CNA record
linux linux_kernel linux:linux_kernel	from 5.6 before 5.10.259; from 5.11 before 5.15.210; from 5.16 before 6.1.176; from 6.2 before 6.6.143; from 6.7 before 6.12.94; from 6.13 before 6.18.36; from 6.19 before 7.0.13; 7.1; and 6 more ranges	NVD

References

References

https://git.kernel.org/stable/c/6564e9c7af7e1dc7bfe7f3093b728abe484d7630	patch
https://git.kernel.org/stable/c/1777ceac4bea5e568a5ad44b7f9bb219c1db21b6	patch
https://git.kernel.org/stable/c/8c6c691bf062dc0753a139a4ab8cb92a70fcf8f3	patch
https://git.kernel.org/stable/c/aa82a078f70f7ff88ba7d1017134e79d1ac140f2	patch
https://git.kernel.org/stable/c/ba21439302db9a82fe4edbed1e38a97271529421	patch
https://git.kernel.org/stable/c/f9b38a8fbfa07f1deaf7ee1eb38fa8b21ea13990	patch
https://git.kernel.org/stable/c/37487d55bf3300e3d2c1368da5c2bd3e3834ea4f	patch
https://git.kernel.org/stable/c/c381039ade2e161ab08c0eda73c4f8b9a7115928	patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.