Local service interruption via uninitialized CAN BCM lock
Published Mar 25, 2026 · Updated Mar 25, 2026
Improper locking in the Linux Kernel CAN BCM subsystem allows local users to cause a service interruption through an RX_RTR_FRAME setup. bcm_rx_setup() allocates an RX bcm_op without initializing bcm_tx_lock, although the RTR receive path invokes bcm_can_tx() and uses that lock. Low-privileged local access and an RX_SETUP operation with RX_RTR_FRAME are required; public records do not specify whether failure manifests as a hang, crash, or another interruption.
Summary
What happened
Improper locking in the Linux Kernel CAN BCM subsystem allows local users to cause a service interruption through an RX_RTR_FRAME setup. bcm_rx_setup() allocates an RX bcm_op without initializing bcm_tx_lock, although the RTR receive path invokes bcm_can_tx() and uses that lock. Low-privileged local access and an RX_SETUP operation with RX_RTR_FRAME are required; public records do not specify whether failure manifests as a hang, crash, or another interruption.
The record
- CVE
- CVE-2026-23362
- Published
- Mar 25, 2026
- Updated
- Mar 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-667, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 25, 2026CVE publishedPublication date reported by the CVE source.
- Mar 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2a437b86ac5a9893c902f30ef66815bf13587bf6 <800f26f11ae37b17f58e0001f28a47dd75c26557
- Affected versionversion=6.15
- Affected versionversion=7595de7bc56e0e52b74e56c90f7e247bf626d628
- Affected versionversion=76c84c3728178b2d38d5604e399dfe8b0752645e <70e951afad4c025261fe3c952d2b07237e320a01
- Affected versionversion=8f1c022541bf5a923c8d6fa483112c15250f30a4
- Affected versionversion=c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 <8215ba7bc99e84e66fd6938874ec4330a9d96518
- Affected versionversion=c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 <c35636e91e392e1540949bbc67932167cb48bc3a
- Affected versionversion=c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 <f0c349b2c21b220af5ba19f29b885e222958d796
- Affected versionversion=c4e8a172501e677ebd8ea9d9161d97dc4df56fbd
- Affected versionversion=cc55dd28c20a6611e30596019b3b2f636819a4c0 <8bcf2d847adb82b2c617456f6da17ac5e6c75285
- Affected versionversion=fbd8fdc2b218e979cfe422b139b8f74c12419d1f
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo