can: bcm: fix data race on rx_stamp/rx_ifindex in bcm_rx_handler()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel c8a5d7cb095d3b12bd9dcf752d6ca0ff50872ac5, Kernel 136de17f38630307991c59aa7080012a99451783, Kernel 4b97410f4bba18d2ee2784c8e089104f387bc27c and 12 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <c8a5d7cb095d3b12bd9dcf752d6ca0ff50872ac5, >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <136de17f38630307991c59aa7080012a99451783, >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <4b97410f4bba18d2ee2784c8e089104f387bc27c, >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <58fd6cbc8541216af1d7ed272ea7ac2b66d50fd8, >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <5f246b96ab47523ec9b8ea870b5c567a3cb1eb1c, >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <656ff69ef235699035e57d9e1ae417e62a38aa7f, >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <b64f60c468d149aca22ea56bb842b9730215aaa5, >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <c312b750bb5ac3348cfc85dab25e90937bd4d251, =2.6.25 | c8a5d7cb095d3b12bd9dcf752d6ca0ff50872ac5, 136de17f38630307991c59aa7080012a99451783, 4b97410f4bba18d2ee2784c8e089104f387bc27c, 58fd6cbc8541216af1d7ed272ea7ac2b66d50fd8, 5f246b96ab47523ec9b8ea870b5c567a3cb1eb1c, 656ff69ef235699035e57d9e1ae417e62a38aa7f, b64f60c468d149aca22ea56bb842b9730215aaa5, c312b750bb5ac3348cfc85dab25e90937bd4d251 |
| linux-kernel: Kernel | >=5.11.0 <5.15.216, >=5.16.0 <6.1.183, >=6.13.0 <6.18.42, >=6.19.0 <7.1.5, >=6.2.0 <6.6.148, >=6.7.0 <6.12.101, >=2.6.25 <5.10.265 | 5.15.216, 6.1.183, 6.18.42, 7.1.5, 6.6.148, 6.12.101, 5.10.265 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket