<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Linux_kernel on CVE Alert &amp; Security Feed</title><link>https://cvealert.net/products/linux_kernel/</link><description>Recent content in Linux_kernel on CVE Alert &amp; Security Feed</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 23 May 2026 12:17:02 +0000</lastBuildDate><atom:link href="https://cvealert.net/products/linux_kernel/index.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-46300</title><link>https://cvealert.net/posts/cve-2026-46300/</link><pubDate>Sat, 23 May 2026 12:17:02 +0000</pubDate><guid>https://cvealert.net/posts/cve-2026-46300/</guid><description>In the Linux kernel, the following vulnerability has been resolved: net: skbuff: preserve shared-frag marker during coalescing skb_try_coalesce() can attach paged frags from @from to @to. If @from has SKBFL_SHARED_FRAG set, the resulting @to skb can contain the same externally-owned or page-cache-backed frags, but the shared-frag marker is currently lost. That breaks the invariant relied on by later in-place writers. In particular, ESP input checks skb_has_shared_frag() before deciding whether an uncloned nonlinear skb can skip skb_cow_data(). If TCP receive coalescing has moved shared frags into an unmarked skb, ESP can see skb_has_shared_frag() as false and decrypt in place over page-cache backed frags. Propagate SKBFL_SHARED_FRAG when skb_try_coalesce() transfers paged frags. The tailroom copy path does not need the marker because it copies bytes into @to&amp;rsquo;s linear data rather than transferring frag descriptors.</description></item></channel></rss>