CVE-2026-52935

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> xfrm: espintcp: do not reuse an in-progress partial send<br /> <br /> espintcp keeps a single in-flight transmit in ctx-&gt;partial.<br /> Before building a new sk_msg, espintcp_sendmsg() first tries to flush<br /> that state through espintcp_push_msgs().<br /> <br /> For blocking callers, espintcp_push_msgs() may return success even when<br /> the previous partial send is still pending. espintcp_sendmsg() would<br /> then reinitialize emsg-&gt;skmsg and reuse ctx-&gt;partial while the old<br /> transfer still owns that state.<br /> <br /> Do not rebuild the send message when ctx-&gt;partial is still in progress.<br /> If espintcp_push_msgs() returns with emsg-&gt;len still set, fail the new<br /> send instead of overwriting the live partial state.<br /> <br /> This is a memory-safety fix: reusing the live partial-send state can<br /> leave a stale offset attached to a new sk_msg and lead to an out-of-<br /> bounds read in the send path.<br /> <br /> tcp_sendmsg_locked() already handles waiting for send buffer memory, so<br /> the fix here is just to preserve espintcp&amp;#39;s one-message-at-a-time<br /> transmit state.