Incorrect CAN statistics via unsynchronized counter updates
Published Aug 15, 2026 · Updated Aug 15, 2026
Race condition in the Linux kernel CAN BCM module allows local users to produce incorrect receive statistics through concurrent CAN frames. The bcm_rx_handler path updated receive statistics and frames_filtered in separate bcm_rx_update_lock sections, allowing one CPU to reset counters between another CPU's updates. Reachability requires an all-interface receive operation and simultaneous frame processing on different CPUs; the documented consequence is bogus, possibly negative, reduction percentages in procfs.
Summary
What happened
Race condition in the Linux kernel CAN BCM module allows local users to produce incorrect receive statistics through concurrent CAN frames. The bcm_rx_handler path updated receive statistics and frames_filtered in separate bcm_rx_update_lock sections, allowing one CPU to reset counters between another CPU's updates. Reachability requires an all-interface receive operation and simultaneous frame processing on different CPUs; the documented consequence is bogus, possibly negative, reduction percentages in procfs.
The record
- CVE
- CVE-2026-72118
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- 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 <8104bcdb2612fdda95169ddc3b49747b2ff98d24
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <8b2783172d92edd650de6006ebd1c800937021ab
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <970caff5c1a63702c80e08d920256bcb5f88ecc5
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <df47f07cdc801a6afe05a486b5a343c3e532a93c
- Affected versionversion=ffd980f976e7fd666c2e61bf8ab35107efd11828 <e6c24ba95fc3f1b5e1dcd28b1c6e59ef61a9daa5
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
No sourced classifications are available.
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