<?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://cve.radiocsirt.org</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>Sun, 04 Oct 2026 03:26:34 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-80613</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-80613</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://cve.radiocsirt.org/vuln/bell-cve-2026-80613</guid>
    </item>
    <item>
      <title>EUVD-2026-361536</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-361536</link>
      <description>EUVD-2026-361536</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-361536</guid>
    </item>
    <item>
      <title>fkie_cve-2026-80613</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-80613</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;veth: fix NAPI leak in XDP enable error path&lt;/p&gt;
&lt;p&gt;During XDP enablement in veth, if xdp_rxq_info_reg() or
xdp_rxq_info_reg_mem_model() fails, the driver rolls back the changes.&lt;/p&gt;
&lt;p&gt;However, the rollback loop:
	for (i--; i &amp;gt;= start; i--) {&lt;/p&gt;
&lt;p&gt;decrements the loop index &amp;#39;i&amp;#39; before the first iteration. This
correctly skips unregistering the rxq for the failed index &amp;#39;i&amp;#39; (as
registration failed or was already cleaned up), but it also
erroneously skips calling netif_napi_deli() for rq[i].xdp_napi.&lt;/p&gt;
&lt;p&gt;Since netif_napi_add() was already called for index &amp;#39;i&amp;#39;, this leaves
a dangling napi_struct in the device&amp;#39;s napi_list. When the veth
device is later destroyed, the freed queue memory (which contains the
leaked NAPI structure) can be reused.&lt;/p&gt;
&lt;p&gt;The subsequent device teardown iterates the NAPI list and
corrupts the reallocated memory, leading to UAF.&lt;/p&gt;
&lt;p&gt;Fix this by explicitly deleting the NAPI association for the failed
index &amp;#39;i&amp;#39; before rolling back the successfully configured queues.&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;veth: fix NAPI leak in XDP enable error path&lt;/p&gt;
&lt;p&gt;During XDP enablement in veth, if xdp_rxq_info_reg() or
xdp_rxq_info_reg_mem_model() fails, the driver rolls back the changes.&lt;/p&gt;
&lt;p&gt;However, the rollback loop:
	for (i--; i &amp;gt;= start; i--) {&lt;/p&gt;
&lt;p&gt;decrements the loop index &amp;#39;i&amp;#39; before the first iteration. This
correctly skips unregistering the rxq for the failed index &amp;#39;i&amp;#39; (as
registration failed or was already cleaned up), but it also
erroneously skips calling netif_napi_deli() for rq[i].xdp_napi.&lt;/p&gt;
&lt;p&gt;Since netif_napi_add() was already called for index &amp;#39;i&amp;#39;, this leaves
a dangling napi_struct in the device&amp;#39;s napi_list. When the veth
device is later destroyed, the freed queue memory (which contains the
leaked NAPI structure) can be reused.&lt;/p&gt;
&lt;p&gt;The subsequent device teardown iterates the NAPI list and
corrupts the reallocated memory, leading to UAF.&lt;/p&gt;
&lt;p&gt;Fix this by explicitly deleting the NAPI association for the failed
index &amp;#39;i&amp;#39; before rolling back the successfully configured queues.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-80613</guid>
    </item>
    <item>
      <title>GHSA-6pj2-mj5g-xmxv</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6pj2-mj5g-xmxv</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;veth: fix NAPI leak in XDP enable error path&lt;/p&gt;
&lt;p&gt;During XDP enablement in veth, if xdp_rxq_info_reg() or
xdp_rxq_info_reg_mem_model() fails, the driver rolls back the changes.&lt;/p&gt;
&lt;p&gt;However, the rollback loop:
	for (i--; i &amp;gt;= start; i--) {&lt;/p&gt;
&lt;p&gt;decrements the loop index &amp;#39;i&amp;#39; before the first iteration. This
correctly skips unregistering the rxq for the failed index &amp;#39;i&amp;#39; (as
registration failed or was already cleaned up), but it also
erroneously skips calling netif_napi_deli() for rq[i].xdp_napi.&lt;/p&gt;
&lt;p&gt;Since netif_napi_add() was already called for index &amp;#39;i&amp;#39;, this leaves
a dangling napi_struct in the device&amp;#39;s napi_list. When the veth
device is later destroyed, the freed queue memory (which contains the
leaked NAPI structure) can be reused.&lt;/p&gt;
&lt;p&gt;The subsequent device teardown iterates the NAPI list and
corrupts the reallocated memory, leading to UAF.&lt;/p&gt;
&lt;p&gt;Fix this by explicitly deleting the NAPI association for the failed
index &amp;#39;i&amp;#39; before rolling back the successfully configured queues.&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;veth: fix NAPI leak in XDP enable error path&lt;/p&gt;
&lt;p&gt;During XDP enablement in veth, if xdp_rxq_info_reg() or
xdp_rxq_info_reg_mem_model() fails, the driver rolls back the changes.&lt;/p&gt;
&lt;p&gt;However, the rollback loop:
	for (i--; i &amp;gt;= start; i--) {&lt;/p&gt;
&lt;p&gt;decrements the loop index &amp;#39;i&amp;#39; before the first iteration. This
correctly skips unregistering the rxq for the failed index &amp;#39;i&amp;#39; (as
registration failed or was already cleaned up), but it also
erroneously skips calling netif_napi_deli() for rq[i].xdp_napi.&lt;/p&gt;
&lt;p&gt;Since netif_napi_add() was already called for index &amp;#39;i&amp;#39;, this leaves
a dangling napi_struct in the device&amp;#39;s napi_list. When the veth
device is later destroyed, the freed queue memory (which contains the
leaked NAPI structure) can be reused.&lt;/p&gt;
&lt;p&gt;The subsequent device teardown iterates the NAPI list and
corrupts the reallocated memory, leading to UAF.&lt;/p&gt;
&lt;p&gt;Fix this by explicitly deleting the NAPI association for the failed
index &amp;#39;i&amp;#39; before rolling back the successfully configured queues.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6pj2-mj5g-xmxv</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-80613</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80613</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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: veth: fix NAPI leak in XDP enable error path During XDP enablement in veth, if xdp_rxq_info_reg() or xdp_rxq_info_reg_mem_model() fails, the driver rolls back the changes. However, the rollback loop: 	for (i--; i &amp;gt;= start; i--) { decrements the loop index &amp;#39;i&amp;#39; before the first iteration. This correctly skips unregistering the rxq for the failed index &amp;#39;i&amp;#39; (as registration failed or was already cleaned up), but it also erroneously skips calling netif_napi_deli() for rq[i].xdp_napi. Since netif_napi_add() was already called for index &amp;#39;i&amp;#39;, this leaves a dangling napi_struct in the device&amp;#39;s napi_list. When the veth device is later destroyed, the freed queue memory (which contains the leaked NAPI structure) can be reused. The subsequent device teardown iterates the NAPI list and corrupts the reallocated memory, leading to UAF. Fix this by explicitly deleting the NAPI association for the failed index &amp;#39;i&amp;#39; before rolling back the successfully configured queues.&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 193 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: veth: fix NAPI leak in XDP enable error path During XDP enablement in veth, if xdp_rxq_info_reg() or xdp_rxq_info_reg_mem_model() fails, the driver rolls back the changes. However, the rollback loop: 	for (i--; i &amp;gt;= start; i--) { decrements the loop index &amp;#39;i&amp;#39; before the first iteration. This correctly skips unregistering the rxq for the failed index &amp;#39;i&amp;#39; (as registration failed or was already cleaned up), but it also erroneously skips calling netif_napi_deli() for rq[i].xdp_napi. Since netif_napi_add() was already called for index &amp;#39;i&amp;#39;, this leaves a dangling napi_struct in the device&amp;#39;s napi_list. When the veth device is later destroyed, the freed queue memory (which contains the leaked NAPI structure) can be reused. The subsequent device teardown iterates the NAPI list and corrupts the reallocated memory, leading to UAF. Fix this by explicitly deleting the NAPI association for the failed index &amp;#39;i&amp;#39; before rolling back the successfully configured queues.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80613</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3075 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3075</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise Speicherbeschädigungen, die Offenlegung oder Manipulation von Daten sowie Denial-of-Service-Zustände.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise Speicherbeschädigungen, die Offenlegung oder Manipulation von Daten sowie Denial-of-Service-Zustände.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3075</guid>
    </item>
  </channel>
</rss>
