<?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>Sat, 03 Oct 2026 01:50:40 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-72341</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-72341</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-72341</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://cve.radiocsirt.org/vuln/certfr-2026-avi-1164</link>
      <description>certfr-2026-avi-1164</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1164</guid>
    </item>
    <item>
      <title>EUVD-2026-353747</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-353747</link>
      <description>EUVD-2026-353747</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-353747</guid>
    </item>
    <item>
      <title>fkie_cve-2026-72341</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-72341</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/mlx5e: Fix publication race for priv-&amp;gt;channel_stats[]&lt;/p&gt;
&lt;p&gt;mlx5e_channel_stats_alloc() publishes a new entry to
priv-&amp;gt;channel_stats[] and then increments priv-&amp;gt;stats_nch as a
publication token, but neither store carries any memory barrier:&lt;/p&gt;
&lt;p&gt;priv-&amp;gt;channel_stats[ix] = kvzalloc_node(...);
	if (!priv-&amp;gt;channel_stats[ix])
		return -ENOMEM;
	priv-&amp;gt;stats_nch++;&lt;/p&gt;
&lt;p&gt;Concurrent readers compute the loop bound from priv-&amp;gt;stats_nch and
then dereference priv-&amp;gt;channel_stats[i] using plain accesses, e.g.&lt;/p&gt;
&lt;p&gt;for (i = 0; i &amp;lt; priv-&amp;gt;stats_nch; i++) {
		struct mlx5e_channel_stats *cs = priv-&amp;gt;channel_stats[i];
		... cs-&amp;gt;rq.packets ...
	}&lt;/p&gt;
&lt;p&gt;On weakly-ordered architectures (ARM, PowerPC, RISC-V) the writes to
channel_stats[ix] and stats_nch may become visible to other CPUs out
of program order. A reader can observe stats_nch == N while still
seeing channel_stats[N-1] == NULL, leading to a NULL pointer
dereference in the channel_stats loop.&lt;/p&gt;
&lt;p&gt;This has been observed in production on BlueField-3 DPUs (arm64),
where ovs-vswitchd queries netdev statistics over netlink during NIC
bringup, racing mlx5e_open_channel() -&amp;gt; mlx5e_channel_stats_alloc()
on another CPU:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address 0x840
  Hardware name: BlueField-3 DPU
  pc : mlx5e_fold_sw_stats64+0x30/0x180 [mlx5_core]
  Call trace:
   mlx5e_fold_sw_stats64+0x30/0x180 [mlx5_core]
   dev_get_stats+0x50/0xc0
   ovs_vport_get_stats+0x38/0xac…&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 publication race for priv-&amp;gt;channel_stats[]&lt;/p&gt;
&lt;p&gt;mlx5e_channel_stats_alloc() publishes a new entry to
priv-&amp;gt;channel_stats[] and then increments priv-&amp;gt;stats_nch as a
publication token, but neither store carries any memory barrier:&lt;/p&gt;
&lt;p&gt;priv-&amp;gt;channel_stats[ix] = kvzalloc_node(...);
	if (!priv-&amp;gt;channel_stats[ix])
		return -ENOMEM;
	priv-&amp;gt;stats_nch++;&lt;/p&gt;
&lt;p&gt;Concurrent readers compute the loop bound from priv-&amp;gt;stats_nch and
then dereference priv-&amp;gt;channel_stats[i] using plain accesses, e.g.&lt;/p&gt;
&lt;p&gt;for (i = 0; i &amp;lt; priv-&amp;gt;stats_nch; i++) {
		struct mlx5e_channel_stats *cs = priv-&amp;gt;channel_stats[i];
		... cs-&amp;gt;rq.packets ...
	}&lt;/p&gt;
&lt;p&gt;On weakly-ordered architectures (ARM, PowerPC, RISC-V) the writes to
channel_stats[ix] and stats_nch may become visible to other CPUs out
of program order. A reader can observe stats_nch == N while still
seeing channel_stats[N-1] == NULL, leading to a NULL pointer
dereference in the channel_stats loop.&lt;/p&gt;
&lt;p&gt;This has been observed in production on BlueField-3 DPUs (arm64),
where ovs-vswitchd queries netdev statistics over netlink during NIC
bringup, racing mlx5e_open_channel() -&amp;gt; mlx5e_channel_stats_alloc()
on another CPU:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address 0x840
  Hardware name: BlueField-3 DPU
  pc : mlx5e_fold_sw_stats64+0x30/0x180 [mlx5_core]
  Call trace:
   mlx5e_fold_sw_stats64+0x30/0x180 [mlx5_core]
   dev_get_stats+0x50/0xc0
   ovs_vport_get_stats+0x38/0xac…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-72341</guid>
    </item>
    <item>
      <title>GHSA-rffj-59x2-vrx3</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rffj-59x2-vrx3</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/mlx5e: Fix publication race for priv-&amp;gt;channel_stats[]&lt;/p&gt;
&lt;p&gt;mlx5e_channel_stats_alloc() publishes a new entry to
priv-&amp;gt;channel_stats[] and then increments priv-&amp;gt;stats_nch as a
publication token, but neither store carries any memory barrier:&lt;/p&gt;
&lt;p&gt;priv-&amp;gt;channel_stats[ix] = kvzalloc_node(...);
	if (!priv-&amp;gt;channel_stats[ix])
		return -ENOMEM;
	priv-&amp;gt;stats_nch++;&lt;/p&gt;
&lt;p&gt;Concurrent readers compute the loop bound from priv-&amp;gt;stats_nch and
then dereference priv-&amp;gt;channel_stats[i] using plain accesses, e.g.&lt;/p&gt;
&lt;p&gt;for (i = 0; i &amp;lt; priv-&amp;gt;stats_nch; i++) {
		struct mlx5e_channel_stats *cs = priv-&amp;gt;channel_stats[i];
		... cs-&amp;gt;rq.packets ...
	}&lt;/p&gt;
&lt;p&gt;On weakly-ordered architectures (ARM, PowerPC, RISC-V) the writes to
channel_stats[ix] and stats_nch may become visible to other CPUs out
of program order. A reader can observe stats_nch == N while still
seeing channel_stats[N-1] == NULL, leading to a NULL pointer
dereference in the channel_stats loop.&lt;/p&gt;
&lt;p&gt;This has been observed in production on BlueField-3 DPUs (arm64),
where ovs-vswitchd queries netdev statistics over netlink during NIC
bringup, racing mlx5e_open_channel() -&amp;gt; mlx5e_channel_stats_alloc()
on another CPU:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address 0x840
  Hardware name: BlueField-3 DPU
  pc : mlx5e_fold_sw_stats64+0x30/0x180 [mlx5_core]
  Call trace:
   mlx5e_fold_sw_stats64+0x30/0x180 [mlx5_core]
   dev_get_stats+0x50/0xc0
   ovs_vport_get_stats+0x38/0xac…&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 publication race for priv-&amp;gt;channel_stats[]&lt;/p&gt;
&lt;p&gt;mlx5e_channel_stats_alloc() publishes a new entry to
priv-&amp;gt;channel_stats[] and then increments priv-&amp;gt;stats_nch as a
publication token, but neither store carries any memory barrier:&lt;/p&gt;
&lt;p&gt;priv-&amp;gt;channel_stats[ix] = kvzalloc_node(...);
	if (!priv-&amp;gt;channel_stats[ix])
		return -ENOMEM;
	priv-&amp;gt;stats_nch++;&lt;/p&gt;
&lt;p&gt;Concurrent readers compute the loop bound from priv-&amp;gt;stats_nch and
then dereference priv-&amp;gt;channel_stats[i] using plain accesses, e.g.&lt;/p&gt;
&lt;p&gt;for (i = 0; i &amp;lt; priv-&amp;gt;stats_nch; i++) {
		struct mlx5e_channel_stats *cs = priv-&amp;gt;channel_stats[i];
		... cs-&amp;gt;rq.packets ...
	}&lt;/p&gt;
&lt;p&gt;On weakly-ordered architectures (ARM, PowerPC, RISC-V) the writes to
channel_stats[ix] and stats_nch may become visible to other CPUs out
of program order. A reader can observe stats_nch == N while still
seeing channel_stats[N-1] == NULL, leading to a NULL pointer
dereference in the channel_stats loop.&lt;/p&gt;
&lt;p&gt;This has been observed in production on BlueField-3 DPUs (arm64),
where ovs-vswitchd queries netdev statistics over netlink during NIC
bringup, racing mlx5e_open_channel() -&amp;gt; mlx5e_channel_stats_alloc()
on another CPU:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address 0x840
  Hardware name: BlueField-3 DPU
  pc : mlx5e_fold_sw_stats64+0x30/0x180 [mlx5_core]
  Call trace:
   mlx5e_fold_sw_stats64+0x30/0x180 [mlx5_core]
   dev_get_stats+0x50/0xc0
   ovs_vport_get_stats+0x38/0xac…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rffj-59x2-vrx3</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-72341 — net/mlx5e: Fix publication race for priv-&gt;channel_stats[]</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-72341</link>
      <description>msrc_CVE-2026-72341</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-72341</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:21910-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/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://cve.radiocsirt.org/vuln/opensuse-su-2026:21910-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23477-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/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://cve.radiocsirt.org/vuln/suse-su-2026:23477-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72341</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72341</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: net/mlx5e: Fix publication race for priv-&amp;gt;channel_stats[] mlx5e_channel_stats_alloc() publishes a new entry to priv-&amp;gt;channel_stats[] and then increments priv-&amp;gt;stats_nch as a publication token, but neither store carries any memory barrier: 	priv-&amp;gt;channel_stats[ix] = kvzalloc_node(...); 	if (!priv-&amp;gt;channel_stats[ix]) 		return -ENOMEM; 	priv-&amp;gt;stats_nch++; Concurrent readers compute the loop bound from priv-&amp;gt;stats_nch and then dereference priv-&amp;gt;channel_stats[i] using plain accesses, e.g. 	for (i = 0; i &amp;lt; priv-&amp;gt;stats_nch; i++) { 		struct mlx5e_channel_stats *cs = priv-&amp;gt;channel_stats[i]; 		... cs-&amp;gt;rq.packets ... 	} On weakly-ordered architectures (ARM, PowerPC, RISC-V) the writes to channel_stats[ix] and stats_nch may become visible to other CPUs out of program order. A reader can observe stats_nch == N while still seeing channel_stats[N-1] == NULL, leading to a NULL pointer dereference in the channel_stats loop. This has been observed in production on BlueField-3 DPUs (arm64), where ovs-vswitchd queries netdev statistics over netlink during NIC bringup, racing mlx5e_open_channel() -&amp;gt; mlx5e_channel_stats_alloc() on another CPU:   Unable to handle kernel NULL pointer dereference at virtual address 0x840   Hardware name: BlueField-3 DPU   pc : mlx5e_fold_sw_stats64+0x30/0x180 [mlx5_core]   Call trace:    mlx5e_fold_sw_stats64+0x30/0x180 [mlx5_core]    dev_get_stats+0x50/0xc0    ovs_vport_get_stats+0x38/0xac [openvsw…&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: net/mlx5e: Fix publication race for priv-&amp;gt;channel_stats[] mlx5e_channel_stats_alloc() publishes a new entry to priv-&amp;gt;channel_stats[] and then increments priv-&amp;gt;stats_nch as a publication token, but neither store carries any memory barrier: 	priv-&amp;gt;channel_stats[ix] = kvzalloc_node(...); 	if (!priv-&amp;gt;channel_stats[ix]) 		return -ENOMEM; 	priv-&amp;gt;stats_nch++; Concurrent readers compute the loop bound from priv-&amp;gt;stats_nch and then dereference priv-&amp;gt;channel_stats[i] using plain accesses, e.g. 	for (i = 0; i &amp;lt; priv-&amp;gt;stats_nch; i++) { 		struct mlx5e_channel_stats *cs = priv-&amp;gt;channel_stats[i]; 		... cs-&amp;gt;rq.packets ... 	} On weakly-ordered architectures (ARM, PowerPC, RISC-V) the writes to channel_stats[ix] and stats_nch may become visible to other CPUs out of program order. A reader can observe stats_nch == N while still seeing channel_stats[N-1] == NULL, leading to a NULL pointer dereference in the channel_stats loop. This has been observed in production on BlueField-3 DPUs (arm64), where ovs-vswitchd queries netdev statistics over netlink during NIC bringup, racing mlx5e_open_channel() -&amp;gt; mlx5e_channel_stats_alloc() on another CPU:   Unable to handle kernel NULL pointer dereference at virtual address 0x840   Hardware name: BlueField-3 DPU   pc : mlx5e_fold_sw_stats64+0x30/0x180 [mlx5_core]   Call trace:    mlx5e_fold_sw_stats64+0x30/0x180 [mlx5_core]    dev_get_stats+0x50/0xc0    ovs_vport_get_stats+0x38/0xac [openvsw…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72341</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, 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 root Rechte zu erlangen, 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://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
