{"dataType": "CVE_RECORD", "dataVersion": "5.1", "cveMetadata": {"cveId": "CVE-2025-37993", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2025-04-16T04:51:23.976Z", "datePublished": "2025-05-29T13:15:52.811Z", "dateUpdated": "2025-05-29T13:15:52.811Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2025-05-29T13:15:52.811Z"}, "descriptions": [{"lang": "en", "value": "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: <none>/-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| [<ffffffff800133e0>] dump_backtrace+0x1c/0x24\n| [<ffffffff800022f2>] show_stack+0x28/0x34\n| [<ffffffff8000de3e>] dump_stack_lvl+0x4a/0x68\n| [<ffffffff8000de70>] dump_stack+0x14/0x1c\n| [<ffffffff80003134>] spin_dump+0x62/0x6e\n| [<ffffffff800883ba>] do_raw_spin_lock+0xd0/0x142\n| [<ffffffff807a6fcc>] _raw_spin_lock_irqsave+0x20/0x2c\n| [<ffffffff80536dba>] m_can_start_xmit+0x90/0x34a\n| [<ffffffff806148b0>] dev_hard_start_xmit+0xa6/0xee\n| [<ffffffff8065b730>] sch_direct_xmit+0x114/0x292\n| [<ffffffff80614e2a>] __dev_queue_xmit+0x3b0/0xaa8\n| [<ffffffff8073b8fa>] can_send+0xc6/0x242\n| [<ffffffff8073d1c0>] raw_sendmsg+0x1a8/0x36c\n| [<ffffffff805ebf06>] sock_write_iter+0x9a/0xee\n| [<ffffffff801d06ea>] vfs_write+0x184/0x3a6\n| [<ffffffff801d0a88>] ksys_write+0xa0/0xc0\n| [<ffffffff801d0abc>] __riscv_sys_write+0x14/0x1c\n| [<ffffffff8079ebf8>] do_trap_ecall_u+0x168/0x212\n| [<ffffffff807a830a>] handle_exception+0x146/0x152\n\nInitializing the spin lock in m_can_class_allocate_dev solves that\nproblem."}], "affected": [{"product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["drivers/net/can/m_can/m_can.c"], "versions": [{"version": "1fa80e23c15051edc1c594270517de3517ded798", "lessThan": "2ecce25ea296f328d79070ee36229a15aeeb7aca", "status": "affected", "versionType": "git"}, {"version": "1fa80e23c15051edc1c594270517de3517ded798", "lessThan": "7d5379cfecfdd665e4206bc4f19824656388779f", "status": "affected", "versionType": "git"}, {"version": "1fa80e23c15051edc1c594270517de3517ded798", "lessThan": "dcaeeb8ae84c5506ebc574732838264f3887738c", "status": "affected", "versionType": "git"}]}, {"product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["drivers/net/can/m_can/m_can.c"], "versions": [{"version": "6.9", "status": "affected"}, {"version": "0", "lessThan": "6.9", "status": "unaffected", "versionType": "semver"}, {"version": "6.12.29", "lessThanOrEqual": "6.12.*", "status": "unaffected", "versionType": "semver"}, {"version": "6.14.7", "lessThanOrEqual": "6.14.*", "status": "unaffected", "versionType": "semver"}, {"version": "6.15", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix"}]}], "cpeApplicability": [{"nodes": [{"operator": "OR", "negate": false, "cpeMatch": [{"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.9", "versionEndExcluding": "6.12.29"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.9", "versionEndExcluding": "6.14.7"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.9", "versionEndExcluding": "6.15"}]}]}], "references": [{"url": "https://git.kernel.org/stable/c/2ecce25ea296f328d79070ee36229a15aeeb7aca"}, {"url": "https://git.kernel.org/stable/c/7d5379cfecfdd665e4206bc4f19824656388779f"}, {"url": "https://git.kernel.org/stable/c/dcaeeb8ae84c5506ebc574732838264f3887738c"}], "title": "can: m_can: m_can_class_allocate_dev(): initialize spin lock on device probe", "x_generator": {"engine": "bippy-1.2.0"}}}}

{}

{"configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "matchCriteriaId": "6AC194F3-971C-45A9-A58B-1814A375C621", "versionEndExcluding": "6.12.29", "versionStartIncluding": "6.9", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "matchCriteriaId": "5715A6F5-A34A-4B27-8A64-82825E963995", "versionEndExcluding": "6.14.7", "versionStartIncluding": "6.13", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:6.15:rc1:*:*:*:*:*:*", "matchCriteriaId": "8D465631-2980-487A-8E65-40AE2B9F8ED1", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:6.15:rc2:*:*:*:*:*:*", "matchCriteriaId": "4C9D071F-B28E-46EC-AC61-22B913390211", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:6.15:rc3:*:*:*:*:*:*", "matchCriteriaId": "13FC0DDE-E513-465E-9E81-515702D49B74", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:6.15:rc4:*:*:*:*:*:*", "matchCriteriaId": "8C7B5B0E-4EEB-48F5-B4CF-0935A7633845", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:6.15:rc5:*:*:*:*:*:*", "matchCriteriaId": "2D240580-3048-49B2-9E27-F115A9DF8224", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "cveTags": [], "descriptions": [{"lang": "en", "value": "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: <none>/-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| [<ffffffff800133e0>] dump_backtrace+0x1c/0x24\n| [<ffffffff800022f2>] show_stack+0x28/0x34\n| [<ffffffff8000de3e>] dump_stack_lvl+0x4a/0x68\n| [<ffffffff8000de70>] dump_stack+0x14/0x1c\n| [<ffffffff80003134>] spin_dump+0x62/0x6e\n| [<ffffffff800883ba>] do_raw_spin_lock+0xd0/0x142\n| [<ffffffff807a6fcc>] _raw_spin_lock_irqsave+0x20/0x2c\n| [<ffffffff80536dba>] m_can_start_xmit+0x90/0x34a\n| [<ffffffff806148b0>] dev_hard_start_xmit+0xa6/0xee\n| [<ffffffff8065b730>] sch_direct_xmit+0x114/0x292\n| [<ffffffff80614e2a>] __dev_queue_xmit+0x3b0/0xaa8\n| [<ffffffff8073b8fa>] can_send+0xc6/0x242\n| [<ffffffff8073d1c0>] raw_sendmsg+0x1a8/0x36c\n| [<ffffffff805ebf06>] sock_write_iter+0x9a/0xee\n| [<ffffffff801d06ea>] vfs_write+0x184/0x3a6\n| [<ffffffff801d0a88>] ksys_write+0xa0/0xc0\n| [<ffffffff801d0abc>] __riscv_sys_write+0x14/0x1c\n| [<ffffffff8079ebf8>] do_trap_ecall_u+0x168/0x212\n| [<ffffffff807a830a>] handle_exception+0x146/0x152\n\nInitializing the spin lock in m_can_class_allocate_dev solves that\nproblem."}, {"lang": "es", "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: can: m_can: m_can_class_allocate_dev(): inicializar spinlock en la sonda del dispositivo. El spinlock tx_handling_spinlock en la estructura m_can_classdev no se est\u00e1 inicializando. Esto provoca la siguiente queja de spinlock bad magic del kernel, p. ej. al intentar enviar tramas CAN con cansend desde can-utils: | BUG: spinlock bad magic en CPU#0, cansend/95 | lock: 0xff60000002ec1010, .magic: 00000000, .owner: /-1, .owner_cpu: 0 | CPU: 0 UID: 0 PID: 95 Comm: cansend No contaminado 6.15.0-rc3-00032-ga79be02bba5c #5 NONE | Nombre del hardware: MachineWare SIM-V (DT) | Rastreo de llamadas: | [] dump_backtrace+0x1c/0x24 | [] show_stack+0x28/0x34 | [] dump_stack_lvl+0x4a/0x68 | [] dump_stack+0x14/0x1c | [] spin_dump+0x62/0x6e | [] do_raw_spin_lock+0xd0/0x142 | [] _raw_spin_lock_irqsave+0x20/0x2c | [] m_can_start_xmit+0x90/0x34a | [] dev_hard_start_xmit+0xa6/0xee | [] sch_direct_xmit+0x114/0x292 | [] __dev_queue_xmit+0x3b0/0xaa8 | [] can_send+0xc6/0x242 | [] raw_sendmsg+0x1a8/0x36c | [] sock_write_iter+0x9a/0xee | [] vfs_write+0x184/0x3a6 | [] ksys_write+0xa0/0xc0 | [] __riscv_sys_write+0x14/0x1c | [] do_trap_ecall_u+0x168/0x212 | [] handle_exception+0x146/0x152 Inicializar el bloqueo de giro en m_can_class_allocate_dev resuelve ese problema."}], "id": "CVE-2025-37993", "lastModified": "2025-11-14T16:59:00.283", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "LOCAL", "availabilityImpact": "HIGH", "baseScore": 5.5, "baseSeverity": "MEDIUM", "confidentialityImpact": "NONE", "integrityImpact": "NONE", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", "version": "3.1"}, "exploitabilityScore": 1.8, "impactScore": 3.6, "source": "nvd@nist.gov", "type": "Primary"}]}, "published": "2025-05-29T14:15:35.767", "references": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/2ecce25ea296f328d79070ee36229a15aeeb7aca"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/7d5379cfecfdd665e4206bc4f19824656388779f"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/dcaeeb8ae84c5506ebc574732838264f3887738c"}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "vulnStatus": "Analyzed", "weaknesses": [{"description": [{"lang": "en", "value": "NVD-CWE-noinfo"}], "source": "nvd@nist.gov", "type": "Primary"}]}

{"bugzilla": {"description": "kernel: can: m_can: m_can_class_allocate_dev(): initialize spin lock on device probe", "id": "2369183", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2369183"}, "csaw": false, "cvss3": {"cvss3_base_score": "7.0", "cvss3_scoring_vector": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H", "status": "draft"}, "details": ["In the Linux kernel, the following vulnerability has been resolved:\ncan: m_can: m_can_class_allocate_dev(): initialize spin lock on device probe\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| BUG: spinlock bad magic on CPU#0, cansend/95\n| lock: 0xff60000002ec1010, .magic: 00000000, .owner: <none>/-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| [<ffffffff800133e0>] dump_backtrace+0x1c/0x24\n| [<ffffffff800022f2>] show_stack+0x28/0x34\n| [<ffffffff8000de3e>] dump_stack_lvl+0x4a/0x68\n| [<ffffffff8000de70>] dump_stack+0x14/0x1c\n| [<ffffffff80003134>] spin_dump+0x62/0x6e\n| [<ffffffff800883ba>] do_raw_spin_lock+0xd0/0x142\n| [<ffffffff807a6fcc>] _raw_spin_lock_irqsave+0x20/0x2c\n| [<ffffffff80536dba>] m_can_start_xmit+0x90/0x34a\n| [<ffffffff806148b0>] dev_hard_start_xmit+0xa6/0xee\n| [<ffffffff8065b730>] sch_direct_xmit+0x114/0x292\n| [<ffffffff80614e2a>] __dev_queue_xmit+0x3b0/0xaa8\n| [<ffffffff8073b8fa>] can_send+0xc6/0x242\n| [<ffffffff8073d1c0>] raw_sendmsg+0x1a8/0x36c\n| [<ffffffff805ebf06>] sock_write_iter+0x9a/0xee\n| [<ffffffff801d06ea>] vfs_write+0x184/0x3a6\n| [<ffffffff801d0a88>] ksys_write+0xa0/0xc0\n| [<ffffffff801d0abc>] __riscv_sys_write+0x14/0x1c\n| [<ffffffff8079ebf8>] do_trap_ecall_u+0x168/0x212\n| [<ffffffff807a830a>] handle_exception+0x146/0x152\nInitializing the spin lock in m_can_class_allocate_dev solves that\nproblem."], "name": "CVE-2025-37993", "package_state": [{"cpe": "cpe:/o:redhat:enterprise_linux:10", "fix_state": "Affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 10"}, {"cpe": "cpe:/o:redhat:enterprise_linux:6", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 6"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 9"}], "public_date": "2025-05-29T00:00:00Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2025-37993\nhttps://nvd.nist.gov/vuln/detail/CVE-2025-37993\nhttps://lore.kernel.org/linux-cve-announce/2025052959-CVE-2025-37993-5c67@gregkh/T"], "threat_severity": "Moderate"}

{"created": "2025-06-24T09:44:22.698154+00:00", "updated": "2025-06-24T09:44:22.698200+00:00", "vendors": ["linux", "linux$PRODUCT$linux_kernel"]}