ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-52935

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

Published Jun 24, 2026 · catalog updated Oct 21, 2026 · xfrm: espintcp: do not

Check if you run it

No confirmed exploitation is on record for CVE-2026-52935. EPSS is 0.10%. Act only if a listed version of xfrm: espintcp: do not is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (xfrm: espintcp: do not).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.10%
Remediation
Not established
Affected products
Linux Kernel

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Linux Kernel5.6.0 → 5.10.259; 5.11.0 → 5.15.210; 5.16.0 → 6.1.176

How to fix CVE-2026-52935

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-52935. EPSS is 0.10%. Act only if a listed version of xfrm: espintcp: do not is installed.

Which versions are affected?

Compare what you have installed with Kernel 5.6.0 → 5.10.259; 5.11.0 → 5.15.210; 5.16.0 → 6.1.176. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.10%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jun 24, 2026 · OpenSSF OSV / OSV Scanner

    Detected

    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 sti

  2. Oct 21, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    Kernel fixed in 5.10.259; Kernel fixed in 5.15.210; Kernel fixed in 6.1.176; Kernel fixed in 6.6.143

  3. Oct 21, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    Kernel fixed in 5.10.259; 5.11.0

  4. Oct 21, 2026 · OpenSSF OSV / OSV Scanner

    Updated

    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 sti

Sources

References

Freshness

Last verified in this catalog Oct 23, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

CVE-2026-52935: xfrm: espintcp: do not reuse an in-progress partial… · ZeroDay Findings