<?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 09:21:09 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64122</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-64122</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-64122</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0926 — 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://cve.radiocsirt.org/vuln/certfr-2026-avi-0926</link>
      <description>certfr-2026-avi-0926</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926</guid>
    </item>
    <item>
      <title>EUVD-2026-348416</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-348416</link>
      <description>EUVD-2026-348416</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-348416</guid>
    </item>
    <item>
      <title>fkie_cve-2026-64122</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-64122</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/mlx5e: Fix use-after-free in mlx5e_tx_reporter_timeout_recover&lt;/p&gt;
&lt;p&gt;mlx5e_tx_reporter_timeout_recover() accesses sq-&amp;gt;netdev after
mlx5e_safe_reopen_channels() has torn down and freed the channel (and
its embedded SQs). Replace the three sq-&amp;gt;netdev references with
priv-&amp;gt;netdev which is safe because priv outlives channel teardown.&lt;/p&gt;
&lt;p&gt;The netdev_err() call already used priv-&amp;gt;netdev for this reason; make
the trylock/unlock and health_channel_eq_recover calls consistent.&lt;/p&gt;
&lt;p&gt;This fixes the following KASAN splat:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: use-after-free in mlx5e_tx_reporter_timeout_recover+0x1dd/0x360 [mlx5_core]
  Read of size 8 at addr ffff889860ed0b28 by task kworker/u113:2/5277&lt;/p&gt;
&lt;p&gt;Call Trace:
   mlx5e_tx_reporter_timeout_recover+0x1dd/0x360 [mlx5_core]
   devlink_health_reporter_recover+0xa2/0x150
   devlink_health_report+0x254/0x7c0
   mlx5e_reporter_tx_timeout+0x297/0x380 [mlx5_core]
   mlx5e_tx_timeout_work+0x109/0x170 [mlx5_core]
   process_one_work+0x677/0xf20
   worker_thread+0x51f/0xd90
   kthread+0x3a5/0x810
   ret_from_fork+0x208/0x400
   ret_from_fork_asm+0x1a/0x30&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;net/mlx5e: Fix use-after-free in mlx5e_tx_reporter_timeout_recover&lt;/p&gt;
&lt;p&gt;mlx5e_tx_reporter_timeout_recover() accesses sq-&amp;gt;netdev after
mlx5e_safe_reopen_channels() has torn down and freed the channel (and
its embedded SQs). Replace the three sq-&amp;gt;netdev references with
priv-&amp;gt;netdev which is safe because priv outlives channel teardown.&lt;/p&gt;
&lt;p&gt;The netdev_err() call already used priv-&amp;gt;netdev for this reason; make
the trylock/unlock and health_channel_eq_recover calls consistent.&lt;/p&gt;
&lt;p&gt;This fixes the following KASAN splat:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: use-after-free in mlx5e_tx_reporter_timeout_recover+0x1dd/0x360 [mlx5_core]
  Read of size 8 at addr ffff889860ed0b28 by task kworker/u113:2/5277&lt;/p&gt;
&lt;p&gt;Call Trace:
   mlx5e_tx_reporter_timeout_recover+0x1dd/0x360 [mlx5_core]
   devlink_health_reporter_recover+0xa2/0x150
   devlink_health_report+0x254/0x7c0
   mlx5e_reporter_tx_timeout+0x297/0x380 [mlx5_core]
   mlx5e_tx_timeout_work+0x109/0x170 [mlx5_core]
   process_one_work+0x677/0xf20
   worker_thread+0x51f/0xd90
   kthread+0x3a5/0x810
   ret_from_fork+0x208/0x400
   ret_from_fork_asm+0x1a/0x30&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-64122</guid>
    </item>
    <item>
      <title>GHSA-q9qw-8fg7-ffww</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-q9qw-8fg7-ffww</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/mlx5e: Fix use-after-free in mlx5e_tx_reporter_timeout_recover&lt;/p&gt;
&lt;p&gt;mlx5e_tx_reporter_timeout_recover() accesses sq-&amp;gt;netdev after
mlx5e_safe_reopen_channels() has torn down and freed the channel (and
its embedded SQs). Replace the three sq-&amp;gt;netdev references with
priv-&amp;gt;netdev which is safe because priv outlives channel teardown.&lt;/p&gt;
&lt;p&gt;The netdev_err() call already used priv-&amp;gt;netdev for this reason; make
the trylock/unlock and health_channel_eq_recover calls consistent.&lt;/p&gt;
&lt;p&gt;This fixes the following KASAN splat:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: use-after-free in mlx5e_tx_reporter_timeout_recover+0x1dd/0x360 [mlx5_core]
  Read of size 8 at addr ffff889860ed0b28 by task kworker/u113:2/5277&lt;/p&gt;
&lt;p&gt;Call Trace:
   mlx5e_tx_reporter_timeout_recover+0x1dd/0x360 [mlx5_core]
   devlink_health_reporter_recover+0xa2/0x150
   devlink_health_report+0x254/0x7c0
   mlx5e_reporter_tx_timeout+0x297/0x380 [mlx5_core]
   mlx5e_tx_timeout_work+0x109/0x170 [mlx5_core]
   process_one_work+0x677/0xf20
   worker_thread+0x51f/0xd90
   kthread+0x3a5/0x810
   ret_from_fork+0x208/0x400
   ret_from_fork_asm+0x1a/0x30&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;net/mlx5e: Fix use-after-free in mlx5e_tx_reporter_timeout_recover&lt;/p&gt;
&lt;p&gt;mlx5e_tx_reporter_timeout_recover() accesses sq-&amp;gt;netdev after
mlx5e_safe_reopen_channels() has torn down and freed the channel (and
its embedded SQs). Replace the three sq-&amp;gt;netdev references with
priv-&amp;gt;netdev which is safe because priv outlives channel teardown.&lt;/p&gt;
&lt;p&gt;The netdev_err() call already used priv-&amp;gt;netdev for this reason; make
the trylock/unlock and health_channel_eq_recover calls consistent.&lt;/p&gt;
&lt;p&gt;This fixes the following KASAN splat:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: use-after-free in mlx5e_tx_reporter_timeout_recover+0x1dd/0x360 [mlx5_core]
  Read of size 8 at addr ffff889860ed0b28 by task kworker/u113:2/5277&lt;/p&gt;
&lt;p&gt;Call Trace:
   mlx5e_tx_reporter_timeout_recover+0x1dd/0x360 [mlx5_core]
   devlink_health_reporter_recover+0xa2/0x150
   devlink_health_report+0x254/0x7c0
   mlx5e_reporter_tx_timeout+0x297/0x380 [mlx5_core]
   mlx5e_tx_timeout_work+0x109/0x170 [mlx5_core]
   process_one_work+0x677/0xf20
   worker_thread+0x51f/0xd90
   kthread+0x3a5/0x810
   ret_from_fork+0x208/0x400
   ret_from_fork_asm+0x1a/0x30&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-q9qw-8fg7-ffww</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64122</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64122</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 111 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix use-after-free in mlx5e_tx_reporter_timeout_recover mlx5e_tx_reporter_timeout_recover() accesses sq-&amp;gt;netdev after mlx5e_safe_reopen_channels() has torn down and freed the channel (and its embedded SQs). Replace the three sq-&amp;gt;netdev references with priv-&amp;gt;netdev which is safe because priv outlives channel teardown. The netdev_err() call already used priv-&amp;gt;netdev for this reason; make the trylock/unlock and health_channel_eq_recover calls consistent. This fixes the following KASAN splat:   BUG: KASAN: use-after-free in mlx5e_tx_reporter_timeout_recover+0x1dd/0x360 [mlx5_core]   Read of size 8 at addr ffff889860ed0b28 by task kworker/u113:2/5277   Call Trace:    mlx5e_tx_reporter_timeout_recover+0x1dd/0x360 [mlx5_core]    devlink_health_reporter_recover+0xa2/0x150    devlink_health_report+0x254/0x7c0    mlx5e_reporter_tx_timeout+0x297/0x380 [mlx5_core]    mlx5e_tx_timeout_work+0x109/0x170 [mlx5_core]    process_one_work+0x677/0xf20    worker_thread+0x51f/0xd90    kthread+0x3a5/0x810    ret_from_fork+0x208/0x400    ret_from_fork_asm+0x1a/0x30&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 111 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix use-after-free in mlx5e_tx_reporter_timeout_recover mlx5e_tx_reporter_timeout_recover() accesses sq-&amp;gt;netdev after mlx5e_safe_reopen_channels() has torn down and freed the channel (and its embedded SQs). Replace the three sq-&amp;gt;netdev references with priv-&amp;gt;netdev which is safe because priv outlives channel teardown. The netdev_err() call already used priv-&amp;gt;netdev for this reason; make the trylock/unlock and health_channel_eq_recover calls consistent. This fixes the following KASAN splat:   BUG: KASAN: use-after-free in mlx5e_tx_reporter_timeout_recover+0x1dd/0x360 [mlx5_core]   Read of size 8 at addr ffff889860ed0b28 by task kworker/u113:2/5277   Call Trace:    mlx5e_tx_reporter_timeout_recover+0x1dd/0x360 [mlx5_core]    devlink_health_reporter_recover+0xa2/0x150    devlink_health_report+0x254/0x7c0    mlx5e_reporter_tx_timeout+0x297/0x380 [mlx5_core]    mlx5e_tx_timeout_work+0x109/0x170 [mlx5_core]    process_one_work+0x677/0xf20    worker_thread+0x51f/0xd90    kthread+0x3a5/0x810    ret_from_fork+0x208/0x400    ret_from_fork_asm+0x1a/0x30&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-64122</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2403 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&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, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403</guid>
    </item>
  </channel>
</rss>
