<?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 20:21:17 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-15551</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-15551</link>
      <description>bdu:2025-15551</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-15551</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-38678</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-38678</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-2025-38678</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0895 — 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-2025-avi-0895</link>
      <description>certfr-2025-avi-0895</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0895</guid>
    </item>
    <item>
      <title>EUVD-2026-347146</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-347146</link>
      <description>EUVD-2026-347146</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-347146</guid>
    </item>
    <item>
      <title>fkie_cve-2025-38678</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-38678</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: nf_tables: reject duplicate device on updates&lt;/p&gt;
&lt;p&gt;A chain/flowtable update with duplicated devices in the same batch is
possible. Unfortunately, netdev event path only removes the first
device that is found, leaving unregistered the hook of the duplicated
device.&lt;/p&gt;
&lt;p&gt;Check if a duplicated device exists in the transaction batch, bail out
with EEXIST in such case.&lt;/p&gt;
&lt;p&gt;WARNING is hit when unregistering the hook:&lt;/p&gt;
&lt;p&gt;[49042.221275] WARNING: CPU: 4 PID: 8425 at net/netfilter/core.c:340 nf_hook_entry_head+0xaa/0x150
 [49042.221375] CPU: 4 UID: 0 PID: 8425 Comm: nft Tainted: G S                  6.16.0+ #170 PREEMPT(full)
 [...]
 [49042.221382] RIP: 0010:nf_hook_entry_head+0xaa/0x150&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;netfilter: nf_tables: reject duplicate device on updates&lt;/p&gt;
&lt;p&gt;A chain/flowtable update with duplicated devices in the same batch is
possible. Unfortunately, netdev event path only removes the first
device that is found, leaving unregistered the hook of the duplicated
device.&lt;/p&gt;
&lt;p&gt;Check if a duplicated device exists in the transaction batch, bail out
with EEXIST in such case.&lt;/p&gt;
&lt;p&gt;WARNING is hit when unregistering the hook:&lt;/p&gt;
&lt;p&gt;[49042.221275] WARNING: CPU: 4 PID: 8425 at net/netfilter/core.c:340 nf_hook_entry_head+0xaa/0x150
 [49042.221375] CPU: 4 UID: 0 PID: 8425 Comm: nft Tainted: G S                  6.16.0+ #170 PREEMPT(full)
 [...]
 [49042.221382] RIP: 0010:nf_hook_entry_head+0xaa/0x150&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-38678</guid>
    </item>
    <item>
      <title>GHSA-g7rm-8pw5-wvg2</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-g7rm-8pw5-wvg2</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: nf_tables: reject duplicate device on updates&lt;/p&gt;
&lt;p&gt;A chain/flowtable update with duplicated devices in the same batch is
possible. Unfortunately, netdev event path only removes the first
device that is found, leaving unregistered the hook of the duplicated
device.&lt;/p&gt;
&lt;p&gt;Check if a duplicated device exists in the transaction batch, bail out
with EEXIST in such case.&lt;/p&gt;
&lt;p&gt;WARNING is hit when unregistering the hook:&lt;/p&gt;
&lt;p&gt;[49042.221275] WARNING: CPU: 4 PID: 8425 at net/netfilter/core.c:340 nf_hook_entry_head+0xaa/0x150
 [49042.221375] CPU: 4 UID: 0 PID: 8425 Comm: nft Tainted: G S                  6.16.0+ #170 PREEMPT(full)
 [...]
 [49042.221382] RIP: 0010:nf_hook_entry_head+0xaa/0x150&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;netfilter: nf_tables: reject duplicate device on updates&lt;/p&gt;
&lt;p&gt;A chain/flowtable update with duplicated devices in the same batch is
possible. Unfortunately, netdev event path only removes the first
device that is found, leaving unregistered the hook of the duplicated
device.&lt;/p&gt;
&lt;p&gt;Check if a duplicated device exists in the transaction batch, bail out
with EEXIST in such case.&lt;/p&gt;
&lt;p&gt;WARNING is hit when unregistering the hook:&lt;/p&gt;
&lt;p&gt;[49042.221275] WARNING: CPU: 4 PID: 8425 at net/netfilter/core.c:340 nf_hook_entry_head+0xaa/0x150
 [49042.221375] CPU: 4 UID: 0 PID: 8425 Comm: nft Tainted: G S                  6.16.0+ #170 PREEMPT(full)
 [...]
 [49042.221382] RIP: 0010:nf_hook_entry_head+0xaa/0x150&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-g7rm-8pw5-wvg2</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-38678 — netfilter: nf_tables: reject duplicate device on updates</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-38678</link>
      <description>msrc_CVE-2025-38678</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-38678</guid>
    </item>
    <item>
      <title>OESA-2026-1337 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-1337</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;md/dm-raid: don&amp;amp;apos;t call md_reap_sync_thread() directly&lt;/p&gt;
&lt;p&gt;Currently md_reap_sync_thread() is called from raid_message() directly
without holding &amp;amp;apos;reconfig_mutex&amp;amp;apos;, this is definitely unsafe because
md_reap_sync_thread() can change many fields that is protected by
&amp;amp;apos;reconfig_mutex&amp;amp;apos;.&lt;/p&gt;
&lt;p&gt;However, hold &amp;amp;apos;reconfig_mutex&amp;amp;apos; here is still problematic because this
will cause deadlock, for example, commit 130443d60b1b (&amp;amp;quot;md: refactor
idle/frozen_sync_thread() to fix deadlock&amp;amp;quot;).&lt;/p&gt;
&lt;p&gt;Fix this problem by using stop_sync_thread() to unregister sync_thread,
like md/raid did.(CVE-2024-35808)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86: fix user address masking non-canonical speculation issue&lt;/p&gt;
&lt;p&gt;It turns out that AMD has a &amp;amp;quot;Meltdown Lite(tm)&amp;amp;quot; issue with non-canonical
accesses in kernel space.  And so using just the high bit to decide
whether an access is in user space or kernel space ends up with the good
old &amp;amp;quot;leak speculative data&amp;amp;quot; if you have the right gadget using the
result:&lt;/p&gt;
&lt;p&gt;CVE-2020-12965 “Transient Execution of Non-Canonical Accesses“&lt;/p&gt;
&lt;p&gt;Now, the kernel surrounds the access with a STAC/CLAC pair, and those
instructions end up serializing execution on older Zen architectures,
which closes the speculation window.&lt;/p&gt;
&lt;p&gt;But that was true only up until Zen 5, which renames t…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;md/dm-raid: don&amp;amp;apos;t call md_reap_sync_thread() directly&lt;/p&gt;
&lt;p&gt;Currently md_reap_sync_thread() is called from raid_message() directly
without holding &amp;amp;apos;reconfig_mutex&amp;amp;apos;, this is definitely unsafe because
md_reap_sync_thread() can change many fields that is protected by
&amp;amp;apos;reconfig_mutex&amp;amp;apos;.&lt;/p&gt;
&lt;p&gt;However, hold &amp;amp;apos;reconfig_mutex&amp;amp;apos; here is still problematic because this
will cause deadlock, for example, commit 130443d60b1b (&amp;amp;quot;md: refactor
idle/frozen_sync_thread() to fix deadlock&amp;amp;quot;).&lt;/p&gt;
&lt;p&gt;Fix this problem by using stop_sync_thread() to unregister sync_thread,
like md/raid did.(CVE-2024-35808)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;x86: fix user address masking non-canonical speculation issue&lt;/p&gt;
&lt;p&gt;It turns out that AMD has a &amp;amp;quot;Meltdown Lite(tm)&amp;amp;quot; issue with non-canonical
accesses in kernel space.  And so using just the high bit to decide
whether an access is in user space or kernel space ends up with the good
old &amp;amp;quot;leak speculative data&amp;amp;quot; if you have the right gadget using the
result:&lt;/p&gt;
&lt;p&gt;CVE-2020-12965 “Transient Execution of Non-Canonical Accesses“&lt;/p&gt;
&lt;p&gt;Now, the kernel surrounds the access with a STAC/CLAC pair, and those
instructions end up serializing execution on older Zen architectures,
which closes the speculation window.&lt;/p&gt;
&lt;p&gt;But that was true only up until Zen 5, which renames t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-1337</guid>
    </item>
    <item>
      <title>openSUSE-SU-2025:20081-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2025:20081-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-2025:20081-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:03600-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:03600-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-2025:03600-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38678</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38678</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 161 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: reject duplicate device on updates A chain/flowtable update with duplicated devices in the same batch is possible. Unfortunately, netdev event path only removes the first device that is found, leaving unregistered the hook of the duplicated device. Check if a duplicated device exists in the transaction batch, bail out with EEXIST in such case. WARNING is hit when unregistering the hook:  [49042.221275] WARNING: CPU: 4 PID: 8425 at net/netfilter/core.c:340 nf_hook_entry_head+0xaa/0x150  [49042.221375] CPU: 4 UID: 0 PID: 8425 Comm: nft Tainted: G S     6.16.0+ #170 PREEMPT(full)  [...]  [49042.221382] RIP: 0010:nf_hook_entry_head+0xaa/0x150&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 161 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: reject duplicate device on updates A chain/flowtable update with duplicated devices in the same batch is possible. Unfortunately, netdev event path only removes the first device that is found, leaving unregistered the hook of the duplicated device. Check if a duplicated device exists in the transaction batch, bail out with EEXIST in such case. WARNING is hit when unregistering the hook:  [49042.221275] WARNING: CPU: 4 PID: 8425 at net/netfilter/core.c:340 nf_hook_entry_head+0xaa/0x150  [49042.221375] CPU: 4 UID: 0 PID: 8425 Comm: nft Tainted: G S     6.16.0+ #170 PREEMPT(full)  [...]  [49042.221382] RIP: 0010:nf_hook_entry_head+0xaa/0x150&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38678</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1965 — Linux Kernel: Schwachstelle ermöglicht Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1965</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann eine Schwachstelle in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann eine Schwachstelle in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1965</guid>
    </item>
  </channel>
</rss>
