{"id":"DEBIAN-CVE-2025-37993","details":"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: \u003cnone\u003e/-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: | [\u003cffffffff800133e0\u003e] dump_backtrace+0x1c/0x24 | [\u003cffffffff800022f2\u003e] show_stack+0x28/0x34 | [\u003cffffffff8000de3e\u003e] dump_stack_lvl+0x4a/0x68 | [\u003cffffffff8000de70\u003e] dump_stack+0x14/0x1c | [\u003cffffffff80003134\u003e] spin_dump+0x62/0x6e | [\u003cffffffff800883ba\u003e] do_raw_spin_lock+0xd0/0x142 | [\u003cffffffff807a6fcc\u003e] _raw_spin_lock_irqsave+0x20/0x2c | [\u003cffffffff80536dba\u003e] m_can_start_xmit+0x90/0x34a | [\u003cffffffff806148b0\u003e] dev_hard_start_xmit+0xa6/0xee | [\u003cffffffff8065b730\u003e] sch_direct_xmit+0x114/0x292 | [\u003cffffffff80614e2a\u003e] __dev_queue_xmit+0x3b0/0xaa8 | [\u003cffffffff8073b8fa\u003e] can_send+0xc6/0x242 | [\u003cffffffff8073d1c0\u003e] raw_sendmsg+0x1a8/0x36c | [\u003cffffffff805ebf06\u003e] sock_write_iter+0x9a/0xee | [\u003cffffffff801d06ea\u003e] vfs_write+0x184/0x3a6 | [\u003cffffffff801d0a88\u003e] ksys_write+0xa0/0xc0 | [\u003cffffffff801d0abc\u003e] __riscv_sys_write+0x14/0x1c | [\u003cffffffff8079ebf8\u003e] do_trap_ecall_u+0x168/0x212 | [\u003cffffffff807a830a\u003e] handle_exception+0x146/0x152  Initializing the spin lock in m_can_class_allocate_dev solves that problem.","modified":"2026-09-01T20:05:47.198807917Z","published":"2025-05-29T14:15:35.767Z","upstream":["CVE-2025-37993"],"references":[{"type":"ADVISORY","url":"https://security-tracker.debian.org/tracker/CVE-2025-37993"}],"affected":[{"package":{"name":"linux","ecosystem":"Debian:13","purl":"pkg:deb/debian/linux?arch=source&distro=trixie"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.29-1"}]}],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2025-37993.json"}},{"package":{"name":"linux","ecosystem":"Debian:14","purl":"pkg:deb/debian/linux?arch=source&distro=forky"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.29-1"}]}],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2025-37993.json"}}],"schema_version":"1.9.0","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"}]}