{"id":"CVE-2025-37993","summary":"can: m_can: m_can_class_allocate_dev(): initialize spin lock on device probe","details":"In the Linux kernel, the following vulnerability has been resolved:\n\ncan: m_can: m_can_class_allocate_dev(): initialize spin lock on device probe\n\nThe spin lock tx_handling_spinlock in struct m_can_classdev is not\nbeing initialized. This leads the following spinlock bad magic\ncomplaint from the kernel, eg. when trying to send CAN frames with\ncansend from can-utils:\n\n| BUG: spinlock bad magic on CPU#0, cansend/95\n|  lock: 0xff60000002ec1010, .magic: 00000000, .owner: \u003cnone\u003e/-1, .owner_cpu: 0\n| CPU: 0 UID: 0 PID: 95 Comm: cansend Not tainted 6.15.0-rc3-00032-ga79be02bba5c #5 NONE\n| Hardware name: MachineWare SIM-V (DT)\n| Call Trace:\n| [\u003cffffffff800133e0\u003e] dump_backtrace+0x1c/0x24\n| [\u003cffffffff800022f2\u003e] show_stack+0x28/0x34\n| [\u003cffffffff8000de3e\u003e] dump_stack_lvl+0x4a/0x68\n| [\u003cffffffff8000de70\u003e] dump_stack+0x14/0x1c\n| [\u003cffffffff80003134\u003e] spin_dump+0x62/0x6e\n| [\u003cffffffff800883ba\u003e] do_raw_spin_lock+0xd0/0x142\n| [\u003cffffffff807a6fcc\u003e] _raw_spin_lock_irqsave+0x20/0x2c\n| [\u003cffffffff80536dba\u003e] m_can_start_xmit+0x90/0x34a\n| [\u003cffffffff806148b0\u003e] dev_hard_start_xmit+0xa6/0xee\n| [\u003cffffffff8065b730\u003e] sch_direct_xmit+0x114/0x292\n| [\u003cffffffff80614e2a\u003e] __dev_queue_xmit+0x3b0/0xaa8\n| [\u003cffffffff8073b8fa\u003e] can_send+0xc6/0x242\n| [\u003cffffffff8073d1c0\u003e] raw_sendmsg+0x1a8/0x36c\n| [\u003cffffffff805ebf06\u003e] sock_write_iter+0x9a/0xee\n| [\u003cffffffff801d06ea\u003e] vfs_write+0x184/0x3a6\n| [\u003cffffffff801d0a88\u003e] ksys_write+0xa0/0xc0\n| [\u003cffffffff801d0abc\u003e] __riscv_sys_write+0x14/0x1c\n| [\u003cffffffff8079ebf8\u003e] do_trap_ecall_u+0x168/0x212\n| [\u003cffffffff807a830a\u003e] handle_exception+0x146/0x152\n\nInitializing the spin lock in m_can_class_allocate_dev solves that\nproblem.","modified":"2026-08-12T03:30:09.253380148Z","published":"2025-05-29T13:15:52.811Z","database_specific":{"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/37xxx/CVE-2025-37993.json","cna_assigner":"Linux"},"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/2ecce25ea296f328d79070ee36229a15aeeb7aca"},{"type":"WEB","url":"https://git.kernel.org/stable/c/7d5379cfecfdd665e4206bc4f19824656388779f"},{"type":"WEB","url":"https://git.kernel.org/stable/c/dcaeeb8ae84c5506ebc574732838264f3887738c"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/37xxx/CVE-2025-37993.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37993"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"1fa80e23c15051edc1c594270517de3517ded798"},{"fixed":"2ecce25ea296f328d79070ee36229a15aeeb7aca"},{"fixed":"7d5379cfecfdd665e4206bc4f19824656388779f"},{"fixed":"dcaeeb8ae84c5506ebc574732838264f3887738c"}]}],"database_specific":{"source":"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2025-37993.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.9.0"},{"fixed":"6.12.29"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.14.7"}]}],"database_specific":{"source":"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2025-37993.json"}}],"schema_version":"1.9.0"}