<?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://db.gcve.eu</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>Thu, 19 Nov 2026 16:57:01 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-37993 — can: m_can: m_can_class_allocate_dev(): initialize spin lock on device probe</title>
      <link>https://db.gcve.eu/vuln/cve-2025-37993</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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://db.gcve.eu/vuln/cve-2025-37993</guid>
    </item>
    <item>
      <title>USN-7699-1 — linux, linux-aws, linux-aws-6.14, linux-gcp, linux-gcp-6.14, linux-oracle, linux-oracle-6.14, linux-raspi, linux-realti…</title>
      <link>https://db.gcve.eu/vuln/usn-7699-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-aws-6.14, Ubuntu:24.04:LTS: linux-gcp-6.14, Ubuntu:24.04:LTS: linux-oracle-6.14&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - RISC-V architecture;
  - x86 architecture;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - GPU drivers;
  - HID subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Network drivers;
  - Mellanox network drivers;
  - PHY drivers;
  - Voltage and Current Regulator drivers;
  - VideoCore services drivers;
  - USB Type-C Connector System Software Interface driver;
  - Xen hypervisor drivers;
  - EROFS file system;
  - Network file system (NFS) client;
  - File systems infrastructure;
  - SMB network file system;
  - Network traffic control;
  - io_uring subsystem;
  - Kernel command line parsing driver;
  - Scheduler infrastructure;
  - Memory management;
  - Networking core;
  - MAC80211 subsystem;
  - Management Component Transport Protocol (MCTP);
  - Netfilter;
  - Open vSwitch;
  - TLS protocol;
  - Wireless networking;
  - SOF drivers;
(CVE-2025-38011, CVE-2025-38095, CVE-2025-37967, CVE-2025-38012,
CVE-2025-38019, CVE-2025-37960, CVE-2025-37973, CVE-2025-37958,
CVE-2025-38094, CVE-2025-37963, CVE-2025-37955, CVE-2025-38014,
CVE-2025-38025, CVE-2025-37970, CVE-2025-37947, CVE-2025-37966,
CVE-2025-37948, CVE-2025-38013, CVE-2025-37957, CVE-2025-38028,
CVE-2025-37962, CVE-2025-38002,…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-aws-6.14, Ubuntu:24.04:LTS: linux-gcp-6.14, Ubuntu:24.04:LTS: linux-oracle-6.14&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - RISC-V architecture;
  - x86 architecture;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - GPU drivers;
  - HID subsystem;
  - IIO ADC drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Network drivers;
  - Mellanox network drivers;
  - PHY drivers;
  - Voltage and Current Regulator drivers;
  - VideoCore services drivers;
  - USB Type-C Connector System Software Interface driver;
  - Xen hypervisor drivers;
  - EROFS file system;
  - Network file system (NFS) client;
  - File systems infrastructure;
  - SMB network file system;
  - Network traffic control;
  - io_uring subsystem;
  - Kernel command line parsing driver;
  - Scheduler infrastructure;
  - Memory management;
  - Networking core;
  - MAC80211 subsystem;
  - Management Component Transport Protocol (MCTP);
  - Netfilter;
  - Open vSwitch;
  - TLS protocol;
  - Wireless networking;
  - SOF drivers;
(CVE-2025-38011, CVE-2025-38095, CVE-2025-37967, CVE-2025-38012,
CVE-2025-38019, CVE-2025-37960, CVE-2025-37973, CVE-2025-37958,
CVE-2025-38094, CVE-2025-37963, CVE-2025-37955, CVE-2025-38014,
CVE-2025-38025, CVE-2025-37970, CVE-2025-37947, CVE-2025-37966,
CVE-2025-37948, CVE-2025-38013, CVE-2025-37957, CVE-2025-38028,
CVE-2025-37962, CVE-2025-38002,…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-7699-1</guid>
    </item>
  </channel>
</rss>
