<?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>Wed, 07 Oct 2026 20:20:19 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-12242</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-12242</link>
      <description>bdu:2025-12242</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-12242</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-37993</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-37993</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-37993</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0721 — 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-2025-avi-0721</link>
      <description>certfr-2025-avi-0721</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0721</guid>
    </item>
    <item>
      <title>EUVD-2026-314362</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314362</link>
      <description>EUVD-2026-314362</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314362</guid>
    </item>
    <item>
      <title>fkie_cve-2025-37993</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-37993</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: m_can: m_can_class_allocate_dev(): initialize spin lock on device probe&lt;/p&gt;
&lt;p&gt;The spin lock tx_handling_spinlock in struct m_can_classdev is not
being initialized. This leads the following spinlock bad magic
complaint from the kernel, eg. when trying to send CAN frames with
cansend from can-utils:&lt;/p&gt;
&lt;p&gt;| BUG: spinlock bad magic on CPU#0, cansend/95
|  lock: 0xff60000002ec1010, .magic: 00000000, .owner: &amp;lt;none&amp;gt;/-1, .owner_cpu: 0
| CPU: 0 UID: 0 PID: 95 Comm: cansend Not tainted 6.15.0-rc3-00032-ga79be02bba5c #5 NONE
| Hardware name: MachineWare SIM-V (DT)
| Call Trace:
| [&amp;lt;ffffffff800133e0&amp;gt;] dump_backtrace+0x1c/0x24
| [&amp;lt;ffffffff800022f2&amp;gt;] show_stack+0x28/0x34
| [&amp;lt;ffffffff8000de3e&amp;gt;] dump_stack_lvl+0x4a/0x68
| [&amp;lt;ffffffff8000de70&amp;gt;] dump_stack+0x14/0x1c
| [&amp;lt;ffffffff80003134&amp;gt;] spin_dump+0x62/0x6e
| [&amp;lt;ffffffff800883ba&amp;gt;] do_raw_spin_lock+0xd0/0x142
| [&amp;lt;ffffffff807a6fcc&amp;gt;] _raw_spin_lock_irqsave+0x20/0x2c
| [&amp;lt;ffffffff80536dba&amp;gt;] m_can_start_xmit+0x90/0x34a
| [&amp;lt;ffffffff806148b0&amp;gt;] dev_hard_start_xmit+0xa6/0xee
| [&amp;lt;ffffffff8065b730&amp;gt;] sch_direct_xmit+0x114/0x292
| [&amp;lt;ffffffff80614e2a&amp;gt;] __dev_queue_xmit+0x3b0/0xaa8
| [&amp;lt;ffffffff8073b8fa&amp;gt;] can_send+0xc6/0x242
| [&amp;lt;ffffffff8073d1c0&amp;gt;] raw_sendmsg+0x1a8/0x36c
| [&amp;lt;ffffffff805ebf06&amp;gt;] sock_write_iter+0x9a/0xee
| [&amp;lt;ffffffff801d06ea&amp;gt;] vfs_write+0x184/0x3a6
| [&amp;lt;ffffffff801d0a88&amp;gt;] ksys_write+0xa0/0xc0
| [&amp;lt;ffffffff801d0abc&amp;gt;] __riscv_sys_write+0x14/0x1c
| [&amp;lt;ffffffff8079ebf8&amp;gt;] do_trap_ecall_u+0…&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;can: m_can: m_can_class_allocate_dev(): initialize spin lock on device probe&lt;/p&gt;
&lt;p&gt;The spin lock tx_handling_spinlock in struct m_can_classdev is not
being initialized. This leads the following spinlock bad magic
complaint from the kernel, eg. when trying to send CAN frames with
cansend from can-utils:&lt;/p&gt;
&lt;p&gt;| BUG: spinlock bad magic on CPU#0, cansend/95
|  lock: 0xff60000002ec1010, .magic: 00000000, .owner: &amp;lt;none&amp;gt;/-1, .owner_cpu: 0
| CPU: 0 UID: 0 PID: 95 Comm: cansend Not tainted 6.15.0-rc3-00032-ga79be02bba5c #5 NONE
| Hardware name: MachineWare SIM-V (DT)
| Call Trace:
| [&amp;lt;ffffffff800133e0&amp;gt;] dump_backtrace+0x1c/0x24
| [&amp;lt;ffffffff800022f2&amp;gt;] show_stack+0x28/0x34
| [&amp;lt;ffffffff8000de3e&amp;gt;] dump_stack_lvl+0x4a/0x68
| [&amp;lt;ffffffff8000de70&amp;gt;] dump_stack+0x14/0x1c
| [&amp;lt;ffffffff80003134&amp;gt;] spin_dump+0x62/0x6e
| [&amp;lt;ffffffff800883ba&amp;gt;] do_raw_spin_lock+0xd0/0x142
| [&amp;lt;ffffffff807a6fcc&amp;gt;] _raw_spin_lock_irqsave+0x20/0x2c
| [&amp;lt;ffffffff80536dba&amp;gt;] m_can_start_xmit+0x90/0x34a
| [&amp;lt;ffffffff806148b0&amp;gt;] dev_hard_start_xmit+0xa6/0xee
| [&amp;lt;ffffffff8065b730&amp;gt;] sch_direct_xmit+0x114/0x292
| [&amp;lt;ffffffff80614e2a&amp;gt;] __dev_queue_xmit+0x3b0/0xaa8
| [&amp;lt;ffffffff8073b8fa&amp;gt;] can_send+0xc6/0x242
| [&amp;lt;ffffffff8073d1c0&amp;gt;] raw_sendmsg+0x1a8/0x36c
| [&amp;lt;ffffffff805ebf06&amp;gt;] sock_write_iter+0x9a/0xee
| [&amp;lt;ffffffff801d06ea&amp;gt;] vfs_write+0x184/0x3a6
| [&amp;lt;ffffffff801d0a88&amp;gt;] ksys_write+0xa0/0xc0
| [&amp;lt;ffffffff801d0abc&amp;gt;] __riscv_sys_write+0x14/0x1c
| [&amp;lt;ffffffff8079ebf8&amp;gt;] do_trap_ecall_u+0…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-37993</guid>
    </item>
    <item>
      <title>GHSA-cc89-xr3w-vpvf</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-cc89-xr3w-vpvf</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: m_can: m_can_class_allocate_dev(): initialize spin lock on device probe&lt;/p&gt;
&lt;p&gt;The spin lock tx_handling_spinlock in struct m_can_classdev is not
being initialized. This leads the following spinlock bad magic
complaint from the kernel, eg. when trying to send CAN frames with
cansend from can-utils:&lt;/p&gt;
&lt;p&gt;| BUG: spinlock bad magic on CPU#0, cansend/95
|  lock: 0xff60000002ec1010, .magic: 00000000, .owner: &amp;lt;none&amp;gt;/-1, .owner_cpu: 0
| CPU: 0 UID: 0 PID: 95 Comm: cansend Not tainted 6.15.0-rc3-00032-ga79be02bba5c #5 NONE
| Hardware name: MachineWare SIM-V (DT)
| Call Trace:
| [&amp;lt;ffffffff800133e0&amp;gt;] dump_backtrace+0x1c/0x24
| [&amp;lt;ffffffff800022f2&amp;gt;] show_stack+0x28/0x34
| [&amp;lt;ffffffff8000de3e&amp;gt;] dump_stack_lvl+0x4a/0x68
| [&amp;lt;ffffffff8000de70&amp;gt;] dump_stack+0x14/0x1c
| [&amp;lt;ffffffff80003134&amp;gt;] spin_dump+0x62/0x6e
| [&amp;lt;ffffffff800883ba&amp;gt;] do_raw_spin_lock+0xd0/0x142
| [&amp;lt;ffffffff807a6fcc&amp;gt;] _raw_spin_lock_irqsave+0x20/0x2c
| [&amp;lt;ffffffff80536dba&amp;gt;] m_can_start_xmit+0x90/0x34a
| [&amp;lt;ffffffff806148b0&amp;gt;] dev_hard_start_xmit+0xa6/0xee
| [&amp;lt;ffffffff8065b730&amp;gt;] sch_direct_xmit+0x114/0x292
| [&amp;lt;ffffffff80614e2a&amp;gt;] __dev_queue_xmit+0x3b0/0xaa8
| [&amp;lt;ffffffff8073b8fa&amp;gt;] can_send+0xc6/0x242
| [&amp;lt;ffffffff8073d1c0&amp;gt;] raw_sendmsg+0x1a8/0x36c
| [&amp;lt;ffffffff805ebf06&amp;gt;] sock_write_iter+0x9a/0xee
| [&amp;lt;ffffffff801d06ea&amp;gt;] vfs_write+0x184/0x3a6
| [&amp;lt;ffffffff801d0a88&amp;gt;] ksys_write+0xa0/0xc0
| [&amp;lt;ffffffff801d0abc&amp;gt;] __riscv_sys_write+0x14/0x1c
| [&amp;lt;ffffffff8079ebf8&amp;gt;] do_trap_ecall_u+0…&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;can: m_can: m_can_class_allocate_dev(): initialize spin lock on device probe&lt;/p&gt;
&lt;p&gt;The spin lock tx_handling_spinlock in struct m_can_classdev is not
being initialized. This leads the following spinlock bad magic
complaint from the kernel, eg. when trying to send CAN frames with
cansend from can-utils:&lt;/p&gt;
&lt;p&gt;| BUG: spinlock bad magic on CPU#0, cansend/95
|  lock: 0xff60000002ec1010, .magic: 00000000, .owner: &amp;lt;none&amp;gt;/-1, .owner_cpu: 0
| CPU: 0 UID: 0 PID: 95 Comm: cansend Not tainted 6.15.0-rc3-00032-ga79be02bba5c #5 NONE
| Hardware name: MachineWare SIM-V (DT)
| Call Trace:
| [&amp;lt;ffffffff800133e0&amp;gt;] dump_backtrace+0x1c/0x24
| [&amp;lt;ffffffff800022f2&amp;gt;] show_stack+0x28/0x34
| [&amp;lt;ffffffff8000de3e&amp;gt;] dump_stack_lvl+0x4a/0x68
| [&amp;lt;ffffffff8000de70&amp;gt;] dump_stack+0x14/0x1c
| [&amp;lt;ffffffff80003134&amp;gt;] spin_dump+0x62/0x6e
| [&amp;lt;ffffffff800883ba&amp;gt;] do_raw_spin_lock+0xd0/0x142
| [&amp;lt;ffffffff807a6fcc&amp;gt;] _raw_spin_lock_irqsave+0x20/0x2c
| [&amp;lt;ffffffff80536dba&amp;gt;] m_can_start_xmit+0x90/0x34a
| [&amp;lt;ffffffff806148b0&amp;gt;] dev_hard_start_xmit+0xa6/0xee
| [&amp;lt;ffffffff8065b730&amp;gt;] sch_direct_xmit+0x114/0x292
| [&amp;lt;ffffffff80614e2a&amp;gt;] __dev_queue_xmit+0x3b0/0xaa8
| [&amp;lt;ffffffff8073b8fa&amp;gt;] can_send+0xc6/0x242
| [&amp;lt;ffffffff8073d1c0&amp;gt;] raw_sendmsg+0x1a8/0x36c
| [&amp;lt;ffffffff805ebf06&amp;gt;] sock_write_iter+0x9a/0xee
| [&amp;lt;ffffffff801d06ea&amp;gt;] vfs_write+0x184/0x3a6
| [&amp;lt;ffffffff801d0a88&amp;gt;] ksys_write+0xa0/0xc0
| [&amp;lt;ffffffff801d0abc&amp;gt;] __riscv_sys_write+0x14/0x1c
| [&amp;lt;ffffffff8079ebf8&amp;gt;] do_trap_ecall_u+0…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-cc89-xr3w-vpvf</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-37993</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-37993</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 83 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: can: m_can: m_can_class_allocate_dev(): initialize spin lock on device probe The spin lock tx_handling_spinlock in struct m_can_classdev is not being initialized. This leads the following spinlock bad magic complaint from the kernel, eg. when trying to send CAN frames with cansend from can-utils: | BUG: spinlock bad magic on CPU#0, cansend/95 |  lock: 0xff60000002ec1010, .magic: 00000000, .owner: &amp;lt;none&amp;gt;/-1, .owner_cpu: 0 | CPU: 0 UID: 0 PID: 95 Comm: cansend Not tainted 6.15.0-rc3-00032-ga79be02bba5c #5 NONE | Hardware name: MachineWare SIM-V (DT) | Call Trace: | [&amp;lt;ffffffff800133e0&amp;gt;] dump_backtrace+0x1c/0x24 | [&amp;lt;ffffffff800022f2&amp;gt;] show_stack+0x28/0x34 | [&amp;lt;ffffffff8000de3e&amp;gt;] dump_stack_lvl+0x4a/0x68 | [&amp;lt;ffffffff8000de70&amp;gt;] dump_stack+0x14/0x1c | [&amp;lt;ffffffff80003134&amp;gt;] spin_dump+0x62/0x6e | [&amp;lt;ffffffff800883ba&amp;gt;] do_raw_spin_lock+0xd0/0x142 | [&amp;lt;ffffffff807a6fcc&amp;gt;] _raw_spin_lock_irqsave+0x20/0x2c | [&amp;lt;ffffffff80536dba&amp;gt;] m_can_start_xmit+0x90/0x34a | [&amp;lt;ffffffff806148b0&amp;gt;] dev_hard_start_xmit+0xa6/0xee | [&amp;lt;ffffffff8065b730&amp;gt;] sch_direct_xmit+0x114/0x292 | [&amp;lt;ffffffff80614e2a&amp;gt;] __dev_queue_xmit+0x3b0/0xaa8 | [&amp;lt;ffffffff8073b8fa&amp;gt;] can_send+0xc6/0x242 | [&amp;lt;ffffffff8073d1c0&amp;gt;] raw_sendmsg+0x1a8/0x36c | [&amp;lt;ffffffff805ebf06&amp;gt;] sock_write_iter+0x9a/0xee | [&amp;lt;ffffffff801d06ea&amp;gt;] vfs_write+0x184/0x3a6 | [&amp;lt;ffffffff801d0a88&amp;gt;] ksys_write+0xa0/0xc0 | [&amp;lt;ffffffff801d0abc&amp;gt;] __riscv_sys_write+0x14/0x1c | [&amp;lt;ffffffff8079ebf8&amp;gt;] do_trap_ecall_u+0x16…&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 83 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: can: m_can: m_can_class_allocate_dev(): initialize spin lock on device probe The spin lock tx_handling_spinlock in struct m_can_classdev is not being initialized. This leads the following spinlock bad magic complaint from the kernel, eg. when trying to send CAN frames with cansend from can-utils: | BUG: spinlock bad magic on CPU#0, cansend/95 |  lock: 0xff60000002ec1010, .magic: 00000000, .owner: &amp;lt;none&amp;gt;/-1, .owner_cpu: 0 | CPU: 0 UID: 0 PID: 95 Comm: cansend Not tainted 6.15.0-rc3-00032-ga79be02bba5c #5 NONE | Hardware name: MachineWare SIM-V (DT) | Call Trace: | [&amp;lt;ffffffff800133e0&amp;gt;] dump_backtrace+0x1c/0x24 | [&amp;lt;ffffffff800022f2&amp;gt;] show_stack+0x28/0x34 | [&amp;lt;ffffffff8000de3e&amp;gt;] dump_stack_lvl+0x4a/0x68 | [&amp;lt;ffffffff8000de70&amp;gt;] dump_stack+0x14/0x1c | [&amp;lt;ffffffff80003134&amp;gt;] spin_dump+0x62/0x6e | [&amp;lt;ffffffff800883ba&amp;gt;] do_raw_spin_lock+0xd0/0x142 | [&amp;lt;ffffffff807a6fcc&amp;gt;] _raw_spin_lock_irqsave+0x20/0x2c | [&amp;lt;ffffffff80536dba&amp;gt;] m_can_start_xmit+0x90/0x34a | [&amp;lt;ffffffff806148b0&amp;gt;] dev_hard_start_xmit+0xa6/0xee | [&amp;lt;ffffffff8065b730&amp;gt;] sch_direct_xmit+0x114/0x292 | [&amp;lt;ffffffff80614e2a&amp;gt;] __dev_queue_xmit+0x3b0/0xaa8 | [&amp;lt;ffffffff8073b8fa&amp;gt;] can_send+0xc6/0x242 | [&amp;lt;ffffffff8073d1c0&amp;gt;] raw_sendmsg+0x1a8/0x36c | [&amp;lt;ffffffff805ebf06&amp;gt;] sock_write_iter+0x9a/0xee | [&amp;lt;ffffffff801d06ea&amp;gt;] vfs_write+0x184/0x3a6 | [&amp;lt;ffffffff801d0a88&amp;gt;] ksys_write+0xa0/0xc0 | [&amp;lt;ffffffff801d0abc&amp;gt;] __riscv_sys_write+0x14/0x1c | [&amp;lt;ffffffff8079ebf8&amp;gt;] do_trap_ecall_u+0x16…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-37993</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1201 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1201</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und weitere nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und weitere nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1201</guid>
    </item>
  </channel>
</rss>
