System disruption via unsynchronized CAN state updates
Published Aug 15, 2026 · Updated Aug 15, 2026
Race condition in the Linux CAN Broadcast Manager allows attackers to corrupt shared state and transmit stale CAN reply frames. bcm_rx_setup() updates timer, filter, and frame fields without synchronizing concurrent receive and timer handlers, while bcm_can_tx() can read a partly overwritten current frame. Reachability requires concurrent BCM setup operations and incoming CAN traffic on a CAN-equipped system; the resulting corruption can inject incorrect bus traffic or crash the kernel.
Summary
What happened
Race condition in the Linux CAN Broadcast Manager allows attackers to corrupt shared state and transmit stale CAN reply frames. bcm_rx_setup() updates timer, filter, and frame fields without synchronizing concurrent receive and timer handlers, while bcm_can_tx() can read a partly overwritten current frame. Reachability requires concurrent BCM setup operations and incoming CAN traffic on a CAN-equipped system; the resulting corruption can inject incorrect bus traffic or crash the kernel.
The record
- CVE
- CVE-2026-72121
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-367, T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 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
- Affected versionversion=5.10.238 <5.11
- Affected versionversion=5.15.185 <5.16
- Affected versionversion=5.4.294 <5.5
- Affected versionversion=6.1.141 <6.2
- Affected versionversion=6.12.31 <6.12.101
- Affected versionversion=6.14.9 <6.15
- Affected versionversion=6.15
- Affected versionversion=6.6.93 <6.6.148
- Affected versionversion=7595de7bc56e0e52b74e56c90f7e247bf626d628
- Affected versionversion=76c84c3728178b2d38d5604e399dfe8b0752645e <a7eb6db1cd3f7b556a301dc1265945ad112089f7
- Affected versionversion=8f1c022541bf5a923c8d6fa483112c15250f30a4
- Affected versionversion=c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 <19b1994069dd29478ba767de1f98f14a088198dc
- Affected versionversion=c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 <749179c2e25b95d22499ed29096b3e02d6dfd2b4
- Affected versionversion=c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 <fc9f5ee1b073bd233d9c604e338af4ebb42cbc33
- Affected versionversion=c4e8a172501e677ebd8ea9d9161d97dc4df56fbd
- Affected versionversion=cc55dd28c20a6611e30596019b3b2f636819a4c0 <834cbca3b12e46887f7a9b35f1981a888360ea4c
- Affected versionversion=fbd8fdc2b218e979cfe422b139b8f74c12419d1f
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
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