<?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 10:30:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38413 — virtio-net: xsk: rx: fix the frame's length check</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38413</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;virtio-net: xsk: rx: fix the frame&amp;#39;s length check&lt;/p&gt;
&lt;p&gt;When calling buf_to_xdp, the len argument is the frame data&amp;#39;s length
without virtio header&amp;#39;s length (vi-&amp;gt;hdr_len). We check that len with&lt;/p&gt;
&lt;p&gt;xsk_pool_get_rx_frame_size() + vi-&amp;gt;hdr_len&lt;/p&gt;
&lt;p&gt;to ensure the provided len does not larger than the allocated chunk
size. The additional vi-&amp;gt;hdr_len is because in virtnet_add_recvbuf_xsk,
we use part of XDP_PACKET_HEADROOM for virtio header and ask the vhost
to start placing data from&lt;/p&gt;
&lt;p&gt;hard_start + XDP_PACKET_HEADROOM - vi-&amp;gt;hdr_len
not
	hard_start + XDP_PACKET_HEADROOM&lt;/p&gt;
&lt;p&gt;But the first buffer has virtio_header, so the maximum frame&amp;#39;s length in
the first buffer can only be&lt;/p&gt;
&lt;p&gt;xsk_pool_get_rx_frame_size()
not
	xsk_pool_get_rx_frame_size() + vi-&amp;gt;hdr_len&lt;/p&gt;
&lt;p&gt;like in the current check.&lt;/p&gt;
&lt;p&gt;This commit adds an additional argument to buf_to_xdp differentiate
between the first buffer and other ones to correctly calculate the maximum
frame&amp;#39;s length.&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;virtio-net: xsk: rx: fix the frame&amp;#39;s length check&lt;/p&gt;
&lt;p&gt;When calling buf_to_xdp, the len argument is the frame data&amp;#39;s length
without virtio header&amp;#39;s length (vi-&amp;gt;hdr_len). We check that len with&lt;/p&gt;
&lt;p&gt;xsk_pool_get_rx_frame_size() + vi-&amp;gt;hdr_len&lt;/p&gt;
&lt;p&gt;to ensure the provided len does not larger than the allocated chunk
size. The additional vi-&amp;gt;hdr_len is because in virtnet_add_recvbuf_xsk,
we use part of XDP_PACKET_HEADROOM for virtio header and ask the vhost
to start placing data from&lt;/p&gt;
&lt;p&gt;hard_start + XDP_PACKET_HEADROOM - vi-&amp;gt;hdr_len
not
	hard_start + XDP_PACKET_HEADROOM&lt;/p&gt;
&lt;p&gt;But the first buffer has virtio_header, so the maximum frame&amp;#39;s length in
the first buffer can only be&lt;/p&gt;
&lt;p&gt;xsk_pool_get_rx_frame_size()
not
	xsk_pool_get_rx_frame_size() + vi-&amp;gt;hdr_len&lt;/p&gt;
&lt;p&gt;like in the current check.&lt;/p&gt;
&lt;p&gt;This commit adds an additional argument to buf_to_xdp differentiate
between the first buffer and other ones to correctly calculate the maximum
frame&amp;#39;s length.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38413</guid>
    </item>
  </channel>
</rss>
