CVE-2026-72117
CVE CVE-2026-72117EUVD EUVD-2026-59075Published 2026-08-15T05:52:56.000ZLast changed 2026-08-19T16:36:08.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 2.6.25; ffd980f976e7fd666c2e61bf8ab35107efd11828 <136de17f38630307991c59aa7080012a99451783; patch: 6.6.148; patch: 7.1.5; ffd980f976e7fd666c2e61bf8ab35107efd11828 <656ff69ef235699035e57d9e1ae417e62a38aa7f; patch: 0; patch: 6.12.101; patch: 5.15.216; patch: 5.10.265; ffd980f976e7fd666c2e61bf8ab35107efd11828 <4b97410f4bba18d2ee2784c8e089104f387bc27c; ffd980f976e7fd666c2e61bf8ab35107efd11828 <b64f60c468d149aca22ea56bb842b9730215aaa5; patch: 6.1.183; patch: 7.2; ffd980f976e7fd666c2e61bf8ab35107efd11828 <5f246b96ab47523ec9b8ea870b5c567a3cb1eb1c; patch: 6.18.42; ffd980f976e7fd666c2e61bf8ab35107efd11828 <58fd6cbc8541216af1d7ed272ea7ac2b66d50fd8; ffd980f976e7fd666c2e61bf8ab35107efd11828 <c312b750bb5ac3348cfc85dab25e90937bd4d251; ffd980f976e7fd666c2e61bf8ab35107efd11828 <c8a5d7cb095d3b12bd9dcf752d6ca0ff50872ac5
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.