<?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://127.0.0.1:10001</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>Sat, 21 Nov 2026 09:55:54 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-38413</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-38413</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2025-38413</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0922 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0922</link>
      <description>certfr-2025-avi-0922</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0922</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38413</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38413</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 86 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: virtio-net: xsk: rx: fix the frame&amp;#39;s length check 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 	xsk_pool_get_rx_frame_size() + vi-&amp;gt;hdr_len 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 	hard_start + XDP_PACKET_HEADROOM - vi-&amp;gt;hdr_len not 	hard_start + XDP_PACKET_HEADROOM But the first buffer has virtio_header, so the maximum frame&amp;#39;s length in the first buffer can only be 	xsk_pool_get_rx_frame_size() not 	xsk_pool_get_rx_frame_size() + vi-&amp;gt;hdr_len like in the current check. 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; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 86 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: virtio-net: xsk: rx: fix the frame&amp;#39;s length check 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 	xsk_pool_get_rx_frame_size() + vi-&amp;gt;hdr_len 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 	hard_start + XDP_PACKET_HEADROOM - vi-&amp;gt;hdr_len not 	hard_start + XDP_PACKET_HEADROOM But the first buffer has virtio_header, so the maximum frame&amp;#39;s length in the first buffer can only be 	xsk_pool_get_rx_frame_size() not 	xsk_pool_get_rx_frame_size() + vi-&amp;gt;hdr_len like in the current check. 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://127.0.0.1:10001/vuln/ubuntu-cve-2025-38413</guid>
    </item>
  </channel>
</rss>
