CVE-2026-72117

UnknownEPSS 0.20%

Last modified

CVE-2026-72117 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.20% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
0.20%

10.2th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= ffd980f976e7fd666c2e61bf8ab35107efd11828, < b64f60c468d149aca22ea56bb842b9730215aaa5; >= ffd980f976e7fd666c2e61bf8ab35107efd11828, < c8a5d7cb095d3b12bd9dcf752d6ca0ff50872ac5; >= ffd980f976e7fd666c2e61bf8ab35107efd11828, < 4b97410f4bba18d2ee2784c8e089104f387bc27c; >= ffd980f976e7fd666c2e61bf8ab35107efd11828, < 5f246b96ab47523ec9b8ea870b5c567a3cb1eb1c; >= ffd980f976e7fd666c2e61bf8ab35107efd11828, < 656ff69ef235699035e57d9e1ae417e62a38aa7f; >= ffd980f976e7fd666c2e61bf8ab35107efd11828, < 136de17f38630307991c59aa7080012a99451783; >= ffd980f976e7fd666c2e61bf8ab35107efd11828, < c312b750bb5ac3348cfc85dab25e90937bd4d251; >= ffd980f976e7fd666c2e61bf8ab35107efd11828, < 58fd6cbc8541216af1d7ed272ea7ac2b66d50fd8
LinuxLinux2.6.25

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is 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.
How severe is CVE-2026-72117?
Severity scoring for CVE-2026-72117 is pending analysis. The EPSS model estimates a 0.20% probability of exploitation in the next 30 days.
How do I fix CVE-2026-72117?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-72117?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST