<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 08:41:47 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-53235 — net: add pskb_may_pull() to skb_gro_receive_list()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-53235</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: add pskb_may_pull() to skb_gro_receive_list()&lt;/p&gt;
&lt;p&gt;skb_gro_receive_list() calls skb_pull(skb, skb_gro_offset(skb)) without
first ensuring the data is in the linear area via pskb_may_pull(). When
the skb arrives via napi_gro_frags(), skb_headlen can be 0 (all data in
page fragments) while skb_gro_offset is non-zero (after IP+TCP header
parsing). The skb_pull() then decrements skb-&amp;gt;len by skb_gro_offset
but skb-&amp;gt;data_len stays unchanged, hitting BUG_ON(skb-&amp;gt;len &amp;lt; skb-&amp;gt;data_len)
in __skb_pull().&lt;/p&gt;
&lt;p&gt;The UDP fraglist GRO path already contains this guard at
udp_offload.c:749. Adding it to skb_gro_receive_list() itself provides
centralized protection for all callers (TCP, UDP, and any future
protocols), and ensures the precondition of skb_pull() is satisfied
before it is called.&lt;/p&gt;
&lt;p&gt;On pskb_may_pull() failure, set NAPI_GRO_CB(skb)-&amp;gt;flush = 1 so the
skb is not held as a new GRO head and is instead delivered through the
normal receive path, matching the UDP handling.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: add pskb_may_pull() to skb_gro_receive_list()&lt;/p&gt;
&lt;p&gt;skb_gro_receive_list() calls skb_pull(skb, skb_gro_offset(skb)) without
first ensuring the data is in the linear area via pskb_may_pull(). When
the skb arrives via napi_gro_frags(), skb_headlen can be 0 (all data in
page fragments) while skb_gro_offset is non-zero (after IP+TCP header
parsing). The skb_pull() then decrements skb-&amp;gt;len by skb_gro_offset
but skb-&amp;gt;data_len stays unchanged, hitting BUG_ON(skb-&amp;gt;len &amp;lt; skb-&amp;gt;data_len)
in __skb_pull().&lt;/p&gt;
&lt;p&gt;The UDP fraglist GRO path already contains this guard at
udp_offload.c:749. Adding it to skb_gro_receive_list() itself provides
centralized protection for all callers (TCP, UDP, and any future
protocols), and ensures the precondition of skb_pull() is satisfied
before it is called.&lt;/p&gt;
&lt;p&gt;On pskb_may_pull() failure, set NAPI_GRO_CB(skb)-&amp;gt;flush = 1 so the
skb is not held as a new GRO head and is instead delivered through the
normal receive path, matching the UDP handling.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-53235</guid>
    </item>
  </channel>
</rss>
