<?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>Thu, 01 Oct 2026 05:59:48 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-74269</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-74269</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-74269</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1164 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://vulnerability.circl.lu/vuln/certfr-2026-avi-1164</link>
      <description>certfr-2026-avi-1164</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/certfr-2026-avi-1164</guid>
    </item>
    <item>
      <title>fkie_cve-2026-74269</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-74269</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bnxt: fix head underflow on XDP head-grow&lt;/p&gt;
&lt;p&gt;The xdp.py test test_xdp_native_adjst_head_grow_data crashes when run on
a bnxt machine (and also crashes in NIPA).&lt;/p&gt;
&lt;p&gt;It seems that the bug is an underflow in bnxt_rx_multi_page_skb, which
builds the skb head:&lt;/p&gt;
&lt;p&gt;napi_build_skb(data_ptr - bp-&amp;gt;rx_offset, rxr-&amp;gt;rx_page_size);&lt;/p&gt;
&lt;p&gt;The problem with this expression is that in page mode, rx_offset is:&lt;/p&gt;
&lt;p&gt;bp-&amp;gt;rx_offset = NET_IP_ALIGN + XDP_PACKET_HEADROOM;&lt;/p&gt;
&lt;p&gt;Which evaluates (at least on x86_64) to 258.&lt;/p&gt;
&lt;p&gt;The test test_xdp_native_adjst_head_grow_data tests a case where the
head is adjusted by -256.&lt;/p&gt;
&lt;p&gt;When this test runs, data_ptr is shifted to frag_start + 2 (where
frag_start = page_address(page) + offset).&lt;/p&gt;
&lt;p&gt;Then, bnxt_rx_multi_page_skb is invoked and the napi_build_skb
expression subtracts 258, landing at an address before frag_start. This
could be either the previous fragment or the previous physical page when
the offset is &amp;lt; 256 (e.g. if the fragment started at offset 0).&lt;/p&gt;
&lt;p&gt;When the skb is freed, the page pool fragment reference is dropped on
either the wrong page or the wrong frag of the right page. In either
case, the corrupted reference count can lead to the page being
prematurely recycled while still in use. Once (incorrectly) recycled, it
can be handed out again and on driver teardown this would result in a
double free.&lt;/p&gt;
&lt;p&gt;The commit under fixes updated this code to handle the case where the
native page size is &amp;gt;= 64k, but it…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bnxt: fix head underflow on XDP head-grow&lt;/p&gt;
&lt;p&gt;The xdp.py test test_xdp_native_adjst_head_grow_data crashes when run on
a bnxt machine (and also crashes in NIPA).&lt;/p&gt;
&lt;p&gt;It seems that the bug is an underflow in bnxt_rx_multi_page_skb, which
builds the skb head:&lt;/p&gt;
&lt;p&gt;napi_build_skb(data_ptr - bp-&amp;gt;rx_offset, rxr-&amp;gt;rx_page_size);&lt;/p&gt;
&lt;p&gt;The problem with this expression is that in page mode, rx_offset is:&lt;/p&gt;
&lt;p&gt;bp-&amp;gt;rx_offset = NET_IP_ALIGN + XDP_PACKET_HEADROOM;&lt;/p&gt;
&lt;p&gt;Which evaluates (at least on x86_64) to 258.&lt;/p&gt;
&lt;p&gt;The test test_xdp_native_adjst_head_grow_data tests a case where the
head is adjusted by -256.&lt;/p&gt;
&lt;p&gt;When this test runs, data_ptr is shifted to frag_start + 2 (where
frag_start = page_address(page) + offset).&lt;/p&gt;
&lt;p&gt;Then, bnxt_rx_multi_page_skb is invoked and the napi_build_skb
expression subtracts 258, landing at an address before frag_start. This
could be either the previous fragment or the previous physical page when
the offset is &amp;lt; 256 (e.g. if the fragment started at offset 0).&lt;/p&gt;
&lt;p&gt;When the skb is freed, the page pool fragment reference is dropped on
either the wrong page or the wrong frag of the right page. In either
case, the corrupted reference count can lead to the page being
prematurely recycled while still in use. Once (incorrectly) recycled, it
can be handed out again and on driver teardown this would result in a
double free.&lt;/p&gt;
&lt;p&gt;The commit under fixes updated this code to handle the case where the
native page size is &amp;gt;= 64k, but it…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-74269</guid>
    </item>
    <item>
      <title>GHSA-qr85-5764-cw3m</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-qr85-5764-cw3m</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bnxt: fix head underflow on XDP head-grow&lt;/p&gt;
&lt;p&gt;The xdp.py test test_xdp_native_adjst_head_grow_data crashes when run on
a bnxt machine (and also crashes in NIPA).&lt;/p&gt;
&lt;p&gt;It seems that the bug is an underflow in bnxt_rx_multi_page_skb, which
builds the skb head:&lt;/p&gt;
&lt;p&gt;napi_build_skb(data_ptr - bp-&amp;gt;rx_offset, rxr-&amp;gt;rx_page_size);&lt;/p&gt;
&lt;p&gt;The problem with this expression is that in page mode, rx_offset is:&lt;/p&gt;
&lt;p&gt;bp-&amp;gt;rx_offset = NET_IP_ALIGN + XDP_PACKET_HEADROOM;&lt;/p&gt;
&lt;p&gt;Which evaluates (at least on x86_64) to 258.&lt;/p&gt;
&lt;p&gt;The test test_xdp_native_adjst_head_grow_data tests a case where the
head is adjusted by -256.&lt;/p&gt;
&lt;p&gt;When this test runs, data_ptr is shifted to frag_start + 2 (where
frag_start = page_address(page) + offset).&lt;/p&gt;
&lt;p&gt;Then, bnxt_rx_multi_page_skb is invoked and the napi_build_skb
expression subtracts 258, landing at an address before frag_start. This
could be either the previous fragment or the previous physical page when
the offset is &amp;lt; 256 (e.g. if the fragment started at offset 0).&lt;/p&gt;
&lt;p&gt;When the skb is freed, the page pool fragment reference is dropped on
either the wrong page or the wrong frag of the right page. In either
case, the corrupted reference count can lead to the page being
prematurely recycled while still in use. Once (incorrectly) recycled, it
can be handed out again and on driver teardown this would result in a
double free.&lt;/p&gt;
&lt;p&gt;The commit under fixes updated this code to handle the case where the
native page size is &amp;gt;= 64k, but it…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bnxt: fix head underflow on XDP head-grow&lt;/p&gt;
&lt;p&gt;The xdp.py test test_xdp_native_adjst_head_grow_data crashes when run on
a bnxt machine (and also crashes in NIPA).&lt;/p&gt;
&lt;p&gt;It seems that the bug is an underflow in bnxt_rx_multi_page_skb, which
builds the skb head:&lt;/p&gt;
&lt;p&gt;napi_build_skb(data_ptr - bp-&amp;gt;rx_offset, rxr-&amp;gt;rx_page_size);&lt;/p&gt;
&lt;p&gt;The problem with this expression is that in page mode, rx_offset is:&lt;/p&gt;
&lt;p&gt;bp-&amp;gt;rx_offset = NET_IP_ALIGN + XDP_PACKET_HEADROOM;&lt;/p&gt;
&lt;p&gt;Which evaluates (at least on x86_64) to 258.&lt;/p&gt;
&lt;p&gt;The test test_xdp_native_adjst_head_grow_data tests a case where the
head is adjusted by -256.&lt;/p&gt;
&lt;p&gt;When this test runs, data_ptr is shifted to frag_start + 2 (where
frag_start = page_address(page) + offset).&lt;/p&gt;
&lt;p&gt;Then, bnxt_rx_multi_page_skb is invoked and the napi_build_skb
expression subtracts 258, landing at an address before frag_start. This
could be either the previous fragment or the previous physical page when
the offset is &amp;lt; 256 (e.g. if the fragment started at offset 0).&lt;/p&gt;
&lt;p&gt;When the skb is freed, the page pool fragment reference is dropped on
either the wrong page or the wrong frag of the right page. In either
case, the corrupted reference count can lead to the page being
prematurely recycled while still in use. Once (incorrectly) recycled, it
can be handed out again and on driver teardown this would result in a
double free.&lt;/p&gt;
&lt;p&gt;The commit under fixes updated this code to handle the case where the
native page size is &amp;gt;= 64k, but it…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-qr85-5764-cw3m</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-74269 — bnxt: fix head underflow on XDP head-grow</title>
      <link>https://vulnerability.circl.lu/vuln/msrc_cve-2026-74269</link>
      <description>msrc_CVE-2026-74269</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/msrc_cve-2026-74269</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:21910-1 — Security update for the Linux Kernel</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:21910-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:21910-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23477-1 — Security update for the Linux Kernel</title>
      <link>https://vulnerability.circl.lu/vuln/suse-su-2026:23477-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/suse-su-2026:23477-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-74269</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-74269</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 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bnxt: fix head underflow on XDP head-grow The xdp.py test test_xdp_native_adjst_head_grow_data crashes when run on a bnxt machine (and also crashes in NIPA). It seems that the bug is an underflow in bnxt_rx_multi_page_skb, which builds the skb head:   napi_build_skb(data_ptr - bp-&amp;gt;rx_offset, rxr-&amp;gt;rx_page_size); The problem with this expression is that in page mode, rx_offset is:   bp-&amp;gt;rx_offset = NET_IP_ALIGN + XDP_PACKET_HEADROOM; Which evaluates (at least on x86_64) to 258. The test test_xdp_native_adjst_head_grow_data tests a case where the head is adjusted by -256. When this test runs, data_ptr is shifted to frag_start + 2 (where frag_start = page_address(page) + offset). Then, bnxt_rx_multi_page_skb is invoked and the napi_build_skb expression subtracts 258, landing at an address before frag_start. This could be either the previous fragment or the previous physical page when the offset is &amp;lt; 256 (e.g. if the fragment started at offset 0). When the skb is freed, the page pool fragment reference is dropped on either the wrong page or the wrong frag of the right page. In either case, the corrupted reference count can lead to the page being prematurely recycled while still in use. Once (incorrectly) recycled, it can be handed out again and on driver teardown this would result in a double free. The commit under fixes updated this code to handle the case where the native page size is &amp;gt;= 64k, but it unintention…&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 154 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bnxt: fix head underflow on XDP head-grow The xdp.py test test_xdp_native_adjst_head_grow_data crashes when run on a bnxt machine (and also crashes in NIPA). It seems that the bug is an underflow in bnxt_rx_multi_page_skb, which builds the skb head:   napi_build_skb(data_ptr - bp-&amp;gt;rx_offset, rxr-&amp;gt;rx_page_size); The problem with this expression is that in page mode, rx_offset is:   bp-&amp;gt;rx_offset = NET_IP_ALIGN + XDP_PACKET_HEADROOM; Which evaluates (at least on x86_64) to 258. The test test_xdp_native_adjst_head_grow_data tests a case where the head is adjusted by -256. When this test runs, data_ptr is shifted to frag_start + 2 (where frag_start = page_address(page) + offset). Then, bnxt_rx_multi_page_skb is invoked and the napi_build_skb expression subtracts 258, landing at an address before frag_start. This could be either the previous fragment or the previous physical page when the offset is &amp;lt; 256 (e.g. if the fragment started at offset 0). When the skb is freed, the page pool fragment reference is dropped on either the wrong page or the wrong frag of the right page. In either case, the corrupted reference count can lead to the page being prematurely recycled while still in use. Once (incorrectly) recycled, it can be handed out again and on driver teardown this would result in a double free. The commit under fixes updated this code to handle the case where the native page size is &amp;gt;= 64k, but it unintention…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-74269</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
