Receive-state corruption via cross-interface timer race
Published Aug 15, 2026 · Updated Aug 15, 2026
A race condition in Linux kernel CAN BCM allows attackers to corrupt receive-operation state via concurrent traffic from several CAN interfaces. The bcm_rx_handler function races timer cancellation or restart against bcm_rx_timeout_handler because ANYDEV operations share rx_ifindex, rx_stamp, and last_frames across interfaces. The condition requires an ANYDEV receive operation with a timeout or throttle timer and matching frames on several interfaces; consequences are spurious timeout notifications and corrupted frame state.
Summary
What happened
A race condition in Linux kernel CAN BCM allows attackers to corrupt receive-operation state via concurrent traffic from several CAN interfaces. The bcm_rx_handler function races timer cancellation or restart against bcm_rx_timeout_handler because ANYDEV operations share rx_ifindex, rx_stamp, and last_frames across interfaces. The condition requires an ANYDEV receive operation with a timeout or throttle timer and matching frames on several interfaces; consequences are spurious timeout notifications and corrupted frame state.
The record
- CVE
- CVE-2026-72115
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-362
- 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=2.6.25
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <18b45251e74e35668f0dd0c470549384ae191ecf
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <2f5976f54a04e9f18b25283036ac3136be453b17
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <3ff8c24b421070a2db99a5cdb86edc9ff339418e
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <b6317022b685a430a3ae420456716e3c0c02ef4b
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <eca8b44d51fc6ab61022258ec968e55e3073b79e
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.
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