CVE-2026-72117

Not scored yetLast modified Nov 6, 2026

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

No CVSS score has been published yet.

Affected software

Source: the vendor's advisory (CNA). 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
Aug 15, 2026
Last modified
Nov 6, 2026
NVD status
Received

Related CVEs from 2026

CVE-2026-72118In the Linux kernel, the following vulnerability has been resolved: can: bcm: fix CAN frame rx/tx statistics KCSAN detected a data race wiCVE-2026-721197.8In the Linux kernel, the following vulnerability has been resolved: can: bcm: extend bcm_tx_lock usage for data and timer updates Stage neCVE-2026-72127.3A security vulnerability has been detected in edvardlindelof notes-mcp up to 0.1.4. This affects an unknown function of the file notes_mcp.pCVE-2026-721207.8In the Linux kernel, the following vulnerability has been resolved: can: bcm: add missing rcu list annotations and operations sashiko-bot CVE-2026-721218.8In the Linux kernel, the following vulnerability has been resolved: can: bcm: add locking when updating filter and timer values KCSAN deteCVE-2026-721227.3In the Linux kernel, the following vulnerability has been resolved: can: bcm: fix lockless bound/ifindex race and silent RX_SETUP failure CVE-2026-721237.8In the Linux kernel, the following vulnerability has been resolved: can: bcm: defer rx_op deallocation to workqueue to fix thrtimer UAF CoCVE-2026-721248.8In the Linux kernel, the following vulnerability has been resolved: can: isotp: serialize TX state transitions under so->rx_lock The TX stCVE-2026-721257.8In the Linux kernel, the following vulnerability has been resolved: can: isotp: fix use-after-free race with concurrent NETDEV_UNREGISTER CVE-2026-721267.8In the Linux kernel, the following vulnerability has been resolved: can: isotp: use unconditional synchronize_rcu() in isotp_release() isoCVE-2026-72127In the Linux kernel, the following vulnerability has been resolved: netdev-genl: report NAPI thread PID in the caller's pid namespace netdCVE-2026-72128In the Linux kernel, the following vulnerability has been resolved: nvmet: fix refcount leak in nvmet_sq_create() In nvmet_sq_create(), a
CVE-2026-72117: Unscored | Vulnix