CVE-2026-72118: Linux kernel · can: bcm: fix CAN frame rx/tx statistics
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in fd75884eae40a7be47867cbfc9fc84a80bb8ddb4 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 17:04 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in fd75884eae40a7be47867cbfc9fc84a80bb8ddb4, e6c24ba95fc3f1b5e1dcd28b1c6e59ef61a9daa5, df47f07cdc801a6afe05a486b5a343c3e532a93c +5
Exploitation evidence
Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: can: bcm: fix CAN frame rx/tx statistics KCSAN detected a data race within the bcm_rx_handler() when two CAN frames have been simultaneously received and processed in a single rx op by two different CPUs. Use atomic operations with (signed) long data types to access the statistics in the hot path to fix the KCSAN complaint. Additionally simplify the update and check of statistics overflow by using the atomic operations in separate bcm_update_[rx|tx]_stats() functions. The rx variant runs under bcm_rx_update_lock to prevent races when resetting the two rx counters; the tx variant runs under bcm_tx_lock and only needs to guard its own counter's overflow. As the rx path resets its values already at LONG_MAX / 100, there is no conflict between the two locking domains (bcm_rx_update_lock vs. bcm_tx_lock) even for ops that use both paths. The rx statistics update and the frames_filtered update in bcm_rx_changed() were previously performed in two separate bcm_rx_update_lock sections. For an rx op subscribed on all interfaces (ifindex == 0), bcm_rx_handler() can run concurrently on different CPUs, so a counter reset by one CPU between these two sections could leave frames_filtered larger than frames_abs on another CPU, producing a bogus (even negative) reduction percentage in procfs. Update the statistics in the same critical section as bcm_rx_changed() to close this gap, which also removes the now unneeded extra lock/unlock pair around the traffic_flags calculation.
References
- git.kernel.org/stable/c/640acf3566fc897065127001be875ebc5401c218 (opens in a new tab)
- git.kernel.org/stable/c/47fca0d1620f2d4fab0677564989ef2b9c225c66 (opens in a new tab)
- git.kernel.org/stable/c/fd75884eae40a7be47867cbfc9fc84a80bb8ddb4 (opens in a new tab)
- git.kernel.org/stable/c/8b2783172d92edd650de6006ebd1c800937021ab (opens in a new tab)
- git.kernel.org/stable/c/970caff5c1a63702c80e08d920256bcb5f88ecc5 (opens in a new tab)
- git.kernel.org/stable/c/8104bcdb2612fdda95169ddc3b49747b2ff98d24 (opens in a new tab)
- git.kernel.org/stable/c/df47f07cdc801a6afe05a486b5a343c3e532a93c (opens in a new tab)
- git.kernel.org/stable/c/e6c24ba95fc3f1b5e1dcd28b1c6e59ef61a9daa5 (opens in a new tab)