CVE-2026-72118can: bcm: fix CAN frame rx/tx statistics
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Aug 19, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from ffd980f976e7fd666c2e61bf8ab35107efd11828 before 640acf3566fc897065127001be875ebc5401c218; from ffd980f976e7fd666c2e61bf8ab35107efd11828 before 47fca0d1620f2d4fab0677564989ef2b9c225c66; from ffd980f976e7fd666c2e61bf8ab35107efd11828 before fd75884eae40a7be47867cbfc9fc84a80bb8ddb4; from ffd980f976e7fd666c2e61bf8ab35107efd11828 before 8b2783172d92edd650de6006ebd1c800937021ab; from ffd980f976e7fd666c2e61bf8ab35107efd11828 before 970caff5c1a63702c80e08d920256bcb5f88ecc5; from ffd980f976e7fd666c2e61bf8ab35107efd11828 before 8104bcdb2612fdda95169ddc3b49747b2ff98d24; from ffd980f976e7fd666c2e61bf8ab35107efd11828 before df47f07cdc801a6afe05a486b5a343c3e532a93c; from ffd980f976e7fd666c2e61bf8ab35107efd11828 before e6c24ba95fc3f1b5e1dcd28b1c6e59ef61a9daa5 | CNA record |
References
- https://git.kernel.org/stable/c/640acf3566fc897065127001be875ebc5401c218
- https://git.kernel.org/stable/c/47fca0d1620f2d4fab0677564989ef2b9c225c66
- https://git.kernel.org/stable/c/fd75884eae40a7be47867cbfc9fc84a80bb8ddb4
- https://git.kernel.org/stable/c/8b2783172d92edd650de6006ebd1c800937021ab
- https://git.kernel.org/stable/c/970caff5c1a63702c80e08d920256bcb5f88ecc5
- https://git.kernel.org/stable/c/8104bcdb2612fdda95169ddc3b49747b2ff98d24
- https://git.kernel.org/stable/c/df47f07cdc801a6afe05a486b5a343c3e532a93c
- https://git.kernel.org/stable/c/e6c24ba95fc3f1b5e1dcd28b1c6e59ef61a9daa5
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.