Frame metadata corruption via unlocked receive updates
Published Aug 15, 2026 · Updated Aug 15, 2026
Missing synchronization in the Linux kernel CAN BCM module allows local users to corrupt timestamp and interface metadata for received frames. The race occurs when one wildcard receive operation runs concurrently on different CPUs for frames arriving on different CAN devices because bcm_rx_handler() writes rx_stamp and rx_ifindex before acquiring bcm_rx_update_lock. Exploitation requires local access to the CAN BCM socket path and concurrent traffic on multiple CAN interfaces; on 32-bit systems, rx_stamp can be torn, and frame content can be paired with metadata from another frame.
Summary
What happened
Missing synchronization in the Linux kernel CAN BCM module allows local users to corrupt timestamp and interface metadata for received frames. The race occurs when one wildcard receive operation runs concurrently on different CPUs for frames arriving on different CAN devices because bcm_rx_handler() writes rx_stamp and rx_ifindex before acquiring bcm_rx_update_lock. Exploitation requires local access to the CAN BCM socket path and concurrent traffic on multiple CAN interfaces; on 32-bit systems, rx_stamp can be torn, and frame content can be paired with metadata from another frame.
The record
- CVE
- CVE-2026-72117
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-820
- Attack vector
- local
- Privileges
- authenticated
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 <136de17f38630307991c59aa7080012a99451783
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <58fd6cbc8541216af1d7ed272ea7ac2b66d50fd8
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <5f246b96ab47523ec9b8ea870b5c567a3cb1eb1c
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <656ff69ef235699035e57d9e1ae417e62a38aa7f
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <c312b750bb5ac3348cfc85dab25e90937bd4d251
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