CVE-2026-72117 json
can: bcm: fix data race on rx_stamp/rx_ifindex in bcm_rx_handler()
published 2026-08-15 2 mo ago modified 2026-11-06 2 d ago also EUVD-2026-59075
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
can: bcm: fix data race on rx_stamp/rx_ifindex in bcm_rx_handler()
For an rx op subscribed on all interfaces (ifindex == 0), the same op is registered once in the shared per-netns wildcard filter list, so bcm_rx_handler() can run concurrently on different CPUs for frames arriving on different net devices.
op->rx_stamp and op->rx_ifindex were written before bcm_rx_update_lock was taken, allowing concurrent writers to race each other - including a torn store of the 64-bit rx_stamp on 32-bit platforms.
Beyond a torn store bcm_send_to_user() must report the timestamp/ifindex of the very same frame whose content it is delivering. So the assignment is placed in the same unbroken bcm_rx_update_lock section as the content comparison.
As a side effect, the RTR-request frame feature (which never reach bcm_send_to_user()) no longer updates rx_stamp/rx_ifindex, since only the notification path needs them.
Patch / fix
- Linux Linux 5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101, 6.18.42, 7.1.5, 7.2
- linux Debian 12 6.1.187-1
- linux Debian 13 6.12.101-1
- linux Debian 14 7.1.5-1
- linux-6.12 Debian 12 6.12.101-1~deb12u1
debian advisories DEBIAN-CVE-2026-72117
- linux Ubuntu 22.04 LTS 5.15.0-198.208
- linux Ubuntu 24.04 LTS 6.8.0-147.147
- linux Ubuntu 26.04 LTS 7.0.0-38.38
- linux-aws Ubuntu 22.04 LTS 5.15.0-1117.124
- linux-aws Ubuntu 24.04 LTS 6.8.0-1067.70
- linux-aws Ubuntu 26.04 LTS 7.0.0-1014.14
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1118.128
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1071.79
ubuntu advisories UBUNTU-CVE-2026-72117
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/b64f60c468d149aca22ea56bb842b9730215aaa5 commit
- git.kernel.org/stable/c/c8a5d7cb095d3b12bd9dcf752d6ca0ff50872ac5 commit
- git.kernel.org/stable/c/4b97410f4bba18d2ee2784c8e089104f387bc27c commit
- git.kernel.org/stable/c/5f246b96ab47523ec9b8ea870b5c567a3cb1eb1c commit
- git.kernel.org/stable/c/656ff69ef235699035e57d9e1ae417e62a38aa7f commit
- git.kernel.org/stable/c/136de17f38630307991c59aa7080012a99451783 commit
- git.kernel.org/stable/c/c312b750bb5ac3348cfc85dab25e90937bd4d251 commit
- git.kernel.org/stable/c/58fd6cbc8541216af1d7ed272ea7ac2b66d50fd8 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-72117 updated cvss 5.5
kernel: can: bcm: fix data race on rx_stamp/rx_ifindex in bcm_rx_handler()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 d ago
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/b64f60c468d149aca22ea56bb842b9730215aaa5
- git.kernel.org /stable/c/c8a5d7cb095d3b12bd9dcf752d6ca0ff50872ac5
- git.kernel.org /stable/c/4b97410f4bba18d2ee2784c8e089104f387bc27c
- git.kernel.org /stable/c/5f246b96ab47523ec9b8ea870b5c567a3cb1eb1c
- git.kernel.org /stable/c/656ff69ef235699035e57d9e1ae417e62a38aa7f
- git.kernel.org /stable/c/136de17f38630307991c59aa7080012a99451783
- git.kernel.org /stable/c/c312b750bb5ac3348cfc85dab25e90937bd4d251
- git.kernel.org /stable/c/58fd6cbc8541216af1d7ed272ea7ac2b66d50fd8
Sources
- CVE List CVE-2026-72117
- NVD CVE-2026-72117
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.