CVE-2026-72117
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.
Affected versions
Linux kernel versions
2.6.25
and later are affected. Fixed in
6.6.148,
6.12.101,
6.18.42,
7.1.5,
7.2-rc4
and their respective stable series.
References
5 totalFrequently asked questions
-
What is CVE-2026-72117?
CVE-2026-72117 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 2.6.25 onward and has been patched in 6.6.148, 6.12.101, 6.18.42 and others. CVE-2026-72117 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-72117?
Yes. CVE-2026-72117 has been patched. Fixed versions include 6.6.148, 6.12.101, 6.18.42 and others. If you are running Linux kernel 2.6.25 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-72117 actively exploited?
No. CVE-2026-72117 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.