CVE-2026-52935·Kernel vulnerability
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.
- Severity
- high
- Software
- Kernel
- Fixed in
- 7.0.13
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.12% — higher than 2% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-52935 scores 7.8 on CVSS, so a successful attack would be serious — but at 0.12%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.19
Until: 7.0.13
Fixed in: 7.0.13
How to fix this CVE
Update your Linux kernel to version 7.0.13 or later to address a critical memory-safety issue in the xfrm espintcp subsystem. The vulnerability allows reuse of an in-progress partial send buffer, which can lead to out-of-bounds memory reads during packet transmission. Systems running kernel versions 6.19 through 7.0.12 should prioritize this update, particularly those using IPSec over TCP for encrypted communications.
sudo dnf update kernel kernel-devel && sudo rebootDefensia detects this vulnerability
How to check if you are affected
- Check installed kernel version: uname -r
- Verify if xfrm and espintcp are in use: grep -i esp /proc/net/xfrm_stat or ps aux | grep -i esp
- Monitor kernel logs for memory access violations: sudo journalctl -k | grep -i 'BUG\|OOPS\|segfault'
- Confirm fix by verifying kernel version is 7.0.13 or higher: uname -r | awk -F. '{if ($1>7 || ($1==7 && $2>=1) || ($1==7 && $2==0 && $3>=13)) print "Patched"; else print "Vulnerable"}'
FAQ
What is CVE-2026-52935?
This is a kernel memory-safety vulnerability in the xfrm espintcp subsystem where an incomplete packet transmission buffer could be incorrectly reused for a new send operation, causing stale memory offsets to be attached to new socket messages. This results in out-of-bounds reads that can crash the kernel or leak sensitive data.
Is CVE-2026-52935 being actively exploited?
No, this vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits have been released. However, the memory-safety nature of the flaw warrants prompt patching.
What versions of Kernel are affected by CVE-2026-52935?
Linux kernel versions 6.19 through 7.0.12 are vulnerable. Version 7.0.13 and later contain the fix.
How do I check if my server is vulnerable to CVE-2026-52935?
Run `uname -r` to display your kernel version. If the output shows 6.19.x through 7.0.12, your system is vulnerable and requires immediate kernel update.
Does Defensia detect CVE-2026-52935?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2026-52935 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/1777ceac4bea5e568a5ad44b7f9bb219c1db21b6
- https://git.kernel.org/stable/c/37487d55bf3300e3d2c1368da5c2bd3e3834ea4f
- https://git.kernel.org/stable/c/6564e9c7af7e1dc7bfe7f3093b728abe484d7630
- https://git.kernel.org/stable/c/8c6c691bf062dc0753a139a4ab8cb92a70fcf8f3
- https://git.kernel.org/stable/c/aa82a078f70f7ff88ba7d1017134e79d1ac140f2
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-52935. Free for 1 server.
Get started free