<?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 01:21:42 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-08865</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-08865</link>
      <description>bdu:2026-08865</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-08865</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-68336</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-68336</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-68336</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0166 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0166</link>
      <description>certfr-2026-avi-0166</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0166</guid>
    </item>
    <item>
      <title>EUVD-2026-347490</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-347490</link>
      <description>EUVD-2026-347490</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-347490</guid>
    </item>
    <item>
      <title>fkie_cve-2025-68336</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-68336</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;locking/spinlock/debug: Fix data-race in do_raw_write_lock&lt;/p&gt;
&lt;p&gt;KCSAN reports:&lt;/p&gt;
&lt;p&gt;BUG: KCSAN: data-race in do_raw_write_lock / do_raw_write_lock&lt;/p&gt;
&lt;p&gt;write (marked) to 0xffff800009cf504c of 4 bytes by task 1102 on cpu 1:
 do_raw_write_lock+0x120/0x204
 _raw_write_lock_irq
 do_exit
 call_usermodehelper_exec_async
 ret_from_fork&lt;/p&gt;
&lt;p&gt;read to 0xffff800009cf504c of 4 bytes by task 1103 on cpu 0:
 do_raw_write_lock+0x88/0x204
 _raw_write_lock_irq
 do_exit
 call_usermodehelper_exec_async
 ret_from_fork&lt;/p&gt;
&lt;p&gt;value changed: 0xffffffff -&amp;gt; 0x00000001&lt;/p&gt;
&lt;p&gt;Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 1103 Comm: kworker/u4:1 6.1.111&lt;/p&gt;
&lt;p&gt;Commit 1a365e822372 (&amp;#34;locking/spinlock/debug: Fix various data races&amp;#34;) has
adressed most of these races, but seems to be not consistent/not complete.&lt;/p&gt;
&lt;p&gt;&amp;gt;From do_raw_write_lock() only debug_write_lock_after() part has been
converted to WRITE_ONCE(), but not debug_write_lock_before() part.
Do it now.&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;locking/spinlock/debug: Fix data-race in do_raw_write_lock&lt;/p&gt;
&lt;p&gt;KCSAN reports:&lt;/p&gt;
&lt;p&gt;BUG: KCSAN: data-race in do_raw_write_lock / do_raw_write_lock&lt;/p&gt;
&lt;p&gt;write (marked) to 0xffff800009cf504c of 4 bytes by task 1102 on cpu 1:
 do_raw_write_lock+0x120/0x204
 _raw_write_lock_irq
 do_exit
 call_usermodehelper_exec_async
 ret_from_fork&lt;/p&gt;
&lt;p&gt;read to 0xffff800009cf504c of 4 bytes by task 1103 on cpu 0:
 do_raw_write_lock+0x88/0x204
 _raw_write_lock_irq
 do_exit
 call_usermodehelper_exec_async
 ret_from_fork&lt;/p&gt;
&lt;p&gt;value changed: 0xffffffff -&amp;gt; 0x00000001&lt;/p&gt;
&lt;p&gt;Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 1103 Comm: kworker/u4:1 6.1.111&lt;/p&gt;
&lt;p&gt;Commit 1a365e822372 (&amp;#34;locking/spinlock/debug: Fix various data races&amp;#34;) has
adressed most of these races, but seems to be not consistent/not complete.&lt;/p&gt;
&lt;p&gt;&amp;gt;From do_raw_write_lock() only debug_write_lock_after() part has been
converted to WRITE_ONCE(), but not debug_write_lock_before() part.
Do it now.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-68336</guid>
    </item>
    <item>
      <title>GHSA-hrvw-g8xf-vhvj</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hrvw-g8xf-vhvj</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;locking/spinlock/debug: Fix data-race in do_raw_write_lock&lt;/p&gt;
&lt;p&gt;KCSAN reports:&lt;/p&gt;
&lt;p&gt;BUG: KCSAN: data-race in do_raw_write_lock / do_raw_write_lock&lt;/p&gt;
&lt;p&gt;write (marked) to 0xffff800009cf504c of 4 bytes by task 1102 on cpu 1:
 do_raw_write_lock+0x120/0x204
 _raw_write_lock_irq
 do_exit
 call_usermodehelper_exec_async
 ret_from_fork&lt;/p&gt;
&lt;p&gt;read to 0xffff800009cf504c of 4 bytes by task 1103 on cpu 0:
 do_raw_write_lock+0x88/0x204
 _raw_write_lock_irq
 do_exit
 call_usermodehelper_exec_async
 ret_from_fork&lt;/p&gt;
&lt;p&gt;value changed: 0xffffffff -&amp;gt; 0x00000001&lt;/p&gt;
&lt;p&gt;Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 1103 Comm: kworker/u4:1 6.1.111&lt;/p&gt;
&lt;p&gt;Commit 1a365e822372 (&amp;#34;locking/spinlock/debug: Fix various data races&amp;#34;) has
adressed most of these races, but seems to be not consistent/not complete.&lt;/p&gt;
&lt;p&gt;&amp;gt;From do_raw_write_lock() only debug_write_lock_after() part has been
converted to WRITE_ONCE(), but not debug_write_lock_before() part.
Do it now.&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;locking/spinlock/debug: Fix data-race in do_raw_write_lock&lt;/p&gt;
&lt;p&gt;KCSAN reports:&lt;/p&gt;
&lt;p&gt;BUG: KCSAN: data-race in do_raw_write_lock / do_raw_write_lock&lt;/p&gt;
&lt;p&gt;write (marked) to 0xffff800009cf504c of 4 bytes by task 1102 on cpu 1:
 do_raw_write_lock+0x120/0x204
 _raw_write_lock_irq
 do_exit
 call_usermodehelper_exec_async
 ret_from_fork&lt;/p&gt;
&lt;p&gt;read to 0xffff800009cf504c of 4 bytes by task 1103 on cpu 0:
 do_raw_write_lock+0x88/0x204
 _raw_write_lock_irq
 do_exit
 call_usermodehelper_exec_async
 ret_from_fork&lt;/p&gt;
&lt;p&gt;value changed: 0xffffffff -&amp;gt; 0x00000001&lt;/p&gt;
&lt;p&gt;Reported by Kernel Concurrency Sanitizer on:
CPU: 0 PID: 1103 Comm: kworker/u4:1 6.1.111&lt;/p&gt;
&lt;p&gt;Commit 1a365e822372 (&amp;#34;locking/spinlock/debug: Fix various data races&amp;#34;) has
adressed most of these races, but seems to be not consistent/not complete.&lt;/p&gt;
&lt;p&gt;&amp;gt;From do_raw_write_lock() only debug_write_lock_after() part has been
converted to WRITE_ONCE(), but not debug_write_lock_before() part.
Do it now.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hrvw-g8xf-vhvj</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-68336 — locking/spinlock/debug: Fix data-race in do_raw_write_lock</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-68336</link>
      <description>msrc_CVE-2025-68336</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-68336</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:10039-1 — kernel-devel-6.18.5-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10039-1</link>
      <description>&lt;p&gt;kernel-devel-6.18.5-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-6.18.5-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:10039-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-68336</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68336</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 227 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: locking/spinlock/debug: Fix data-race in do_raw_write_lock KCSAN reports: BUG: KCSAN: data-race in do_raw_write_lock / do_raw_write_lock write (marked) to 0xffff800009cf504c of 4 bytes by task 1102 on cpu 1:  do_raw_write_lock+0x120/0x204  _raw_write_lock_irq  do_exit  call_usermodehelper_exec_async  ret_from_fork read to 0xffff800009cf504c of 4 bytes by task 1103 on cpu 0:  do_raw_write_lock+0x88/0x204  _raw_write_lock_irq  do_exit  call_usermodehelper_exec_async  ret_from_fork value changed: 0xffffffff -&amp;gt; 0x00000001 Reported by Kernel Concurrency Sanitizer on: CPU: 0 PID: 1103 Comm: kworker/u4:1 6.1.111 Commit 1a365e822372 (&amp;#34;locking/spinlock/debug: Fix various data races&amp;#34;) has adressed most of these races, but seems to be not consistent/not complete. &amp;gt;From do_raw_write_lock() only debug_write_lock_after() part has been converted to WRITE_ONCE(), but not debug_write_lock_before() part. Do it now.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 227 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: locking/spinlock/debug: Fix data-race in do_raw_write_lock KCSAN reports: BUG: KCSAN: data-race in do_raw_write_lock / do_raw_write_lock write (marked) to 0xffff800009cf504c of 4 bytes by task 1102 on cpu 1:  do_raw_write_lock+0x120/0x204  _raw_write_lock_irq  do_exit  call_usermodehelper_exec_async  ret_from_fork read to 0xffff800009cf504c of 4 bytes by task 1103 on cpu 0:  do_raw_write_lock+0x88/0x204  _raw_write_lock_irq  do_exit  call_usermodehelper_exec_async  ret_from_fork value changed: 0xffffffff -&amp;gt; 0x00000001 Reported by Kernel Concurrency Sanitizer on: CPU: 0 PID: 1103 Comm: kworker/u4:1 6.1.111 Commit 1a365e822372 (&amp;#34;locking/spinlock/debug: Fix various data races&amp;#34;) has adressed most of these races, but seems to be not consistent/not complete. &amp;gt;From do_raw_write_lock() only debug_write_lock_after() part has been converted to WRITE_ONCE(), but not debug_write_lock_before() part. Do it now.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-68336</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2914 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2914</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschrieben Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschrieben Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2914</guid>
    </item>
  </channel>
</rss>
