<?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>Mon, 28 Sep 2026 22:51:18 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-97574</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-97574</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bnxt_en: Don&amp;#39;t free the live ring&amp;#39;s TPA state on queue restart failure&lt;/p&gt;
&lt;p&gt;bnxt_queue_mem_alloc() shallow copies the live RX ring into the clone:&lt;/p&gt;
&lt;p&gt;memcpy(clone, rxr, sizeof(*rxr));&lt;/p&gt;
&lt;p&gt;the code currently clears pointers that the clone owns (such as
rx_agg_bmap), but rx_tpa and rx_tpa_idx_map are left pointing at memory
of the live ring that was cloned.&lt;/p&gt;
&lt;p&gt;If an allocation failure happens later and the err_free_tpa_info label
is taken, the live ring&amp;#39;s memory can be freed while still in use.&lt;/p&gt;
&lt;p&gt;Fix this by initializing the clone&amp;#39;s pointers to NULL to prevent live
ring state from being freed inadvertently.&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_en: Don&amp;#39;t free the live ring&amp;#39;s TPA state on queue restart failure&lt;/p&gt;
&lt;p&gt;bnxt_queue_mem_alloc() shallow copies the live RX ring into the clone:&lt;/p&gt;
&lt;p&gt;memcpy(clone, rxr, sizeof(*rxr));&lt;/p&gt;
&lt;p&gt;the code currently clears pointers that the clone owns (such as
rx_agg_bmap), but rx_tpa and rx_tpa_idx_map are left pointing at memory
of the live ring that was cloned.&lt;/p&gt;
&lt;p&gt;If an allocation failure happens later and the err_free_tpa_info label
is taken, the live ring&amp;#39;s memory can be freed while still in use.&lt;/p&gt;
&lt;p&gt;Fix this by initializing the clone&amp;#39;s pointers to NULL to prevent live
ring state from being freed inadvertently.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-97574</guid>
    </item>
    <item>
      <title>GHSA-3q52-v35w-h242</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-3q52-v35w-h242</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bnxt_en: Don&amp;#39;t free the live ring&amp;#39;s TPA state on queue restart failure&lt;/p&gt;
&lt;p&gt;bnxt_queue_mem_alloc() shallow copies the live RX ring into the clone:&lt;/p&gt;
&lt;p&gt;memcpy(clone, rxr, sizeof(*rxr));&lt;/p&gt;
&lt;p&gt;the code currently clears pointers that the clone owns (such as
rx_agg_bmap), but rx_tpa and rx_tpa_idx_map are left pointing at memory
of the live ring that was cloned.&lt;/p&gt;
&lt;p&gt;If an allocation failure happens later and the err_free_tpa_info label
is taken, the live ring&amp;#39;s memory can be freed while still in use.&lt;/p&gt;
&lt;p&gt;Fix this by initializing the clone&amp;#39;s pointers to NULL to prevent live
ring state from being freed inadvertently.&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_en: Don&amp;#39;t free the live ring&amp;#39;s TPA state on queue restart failure&lt;/p&gt;
&lt;p&gt;bnxt_queue_mem_alloc() shallow copies the live RX ring into the clone:&lt;/p&gt;
&lt;p&gt;memcpy(clone, rxr, sizeof(*rxr));&lt;/p&gt;
&lt;p&gt;the code currently clears pointers that the clone owns (such as
rx_agg_bmap), but rx_tpa and rx_tpa_idx_map are left pointing at memory
of the live ring that was cloned.&lt;/p&gt;
&lt;p&gt;If an allocation failure happens later and the err_free_tpa_info label
is taken, the live ring&amp;#39;s memory can be freed while still in use.&lt;/p&gt;
&lt;p&gt;Fix this by initializing the clone&amp;#39;s pointers to NULL to prevent live
ring state from being freed inadvertently.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-3q52-v35w-h242</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-97574</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-97574</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Don&amp;#39;t free the live ring&amp;#39;s TPA state on queue restart failure bnxt_queue_mem_alloc() shallow copies the live RX ring into the clone:   memcpy(clone, rxr, sizeof(*rxr)); the code currently clears pointers that the clone owns (such as rx_agg_bmap), but rx_tpa and rx_tpa_idx_map are left pointing at memory of the live ring that was cloned. If an allocation failure happens later and the err_free_tpa_info label is taken, the live ring&amp;#39;s memory can be freed while still in use. Fix this by initializing the clone&amp;#39;s pointers to NULL to prevent live ring state from being freed inadvertently.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Don&amp;#39;t free the live ring&amp;#39;s TPA state on queue restart failure bnxt_queue_mem_alloc() shallow copies the live RX ring into the clone:   memcpy(clone, rxr, sizeof(*rxr)); the code currently clears pointers that the clone owns (such as rx_agg_bmap), but rx_tpa and rx_tpa_idx_map are left pointing at memory of the live ring that was cloned. If an allocation failure happens later and the err_free_tpa_info label is taken, the live ring&amp;#39;s memory can be freed while still in use. Fix this by initializing the clone&amp;#39;s pointers to NULL to prevent live ring state from being freed inadvertently.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-97574</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3579 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</guid>
    </item>
  </channel>
</rss>
