CVE-2026-72118can: bcm: fix CAN frame rx/tx statistics
- —Not scoredno CVSS score yet
- 0.22%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.22% · top 88% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < 640acf3566fc897065127001be875ebc5401c218
- affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < 47fca0d1620f2d4fab0677564989ef2b9c225c66
- affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < fd75884eae40a7be47867cbfc9fc84a80bb8ddb4
- affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < 8b2783172d92edd650de6006ebd1c800937021ab
- affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < 970caff5c1a63702c80e08d920256bcb5f88ecc5
- affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < 8104bcdb2612fdda95169ddc3b49747b2ff98d24
- affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < df47f07cdc801a6afe05a486b5a343c3e532a93c
- affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < e6c24ba95fc3f1b5e1dcd28b1c6e59ef61a9daa5
- affected 2.6.25
- unaffected < 2.6.25
- unaffected 5.10.265 – ≤ 5.10.*
- unaffected 5.15.216 – ≤ 5.15.*
- unaffected 6.1.183 – ≤ 6.1.*
- unaffected 6.6.148 – ≤ 6.6.*
- unaffected 6.12.101 – ≤ 6.12.*
- unaffected 6.18.42 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/640acf3566fc897065127001be875ebc5401c218 (opens in a new tab)
- https://git.kernel.org/stable/c/47fca0d1620f2d4fab0677564989ef2b9c225c66 (opens in a new tab)
- https://git.kernel.org/stable/c/fd75884eae40a7be47867cbfc9fc84a80bb8ddb4 (opens in a new tab)
- https://git.kernel.org/stable/c/8b2783172d92edd650de6006ebd1c800937021ab (opens in a new tab)
- https://git.kernel.org/stable/c/970caff5c1a63702c80e08d920256bcb5f88ecc5 (opens in a new tab)
- https://git.kernel.org/stable/c/8104bcdb2612fdda95169ddc3b49747b2ff98d24 (opens in a new tab)
- https://git.kernel.org/stable/c/df47f07cdc801a6afe05a486b5a343c3e532a93c (opens in a new tab)
- https://git.kernel.org/stable/c/e6c24ba95fc3f1b5e1dcd28b1c6e59ef61a9daa5 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-59076 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-72118)Record last updated .