CVE-2026-72117None▾ SunlitIn 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 shar…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Nov 6.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
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.
Linux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < b64f60c468d149aca22ea56bb842b9730215aaa5Linux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < c8a5d7cb095d3b12bd9dcf752d6ca0ff50872ac5Linux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < 4b97410f4bba18d2ee2784c8e089104f387bc27cLinux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < 5f246b96ab47523ec9b8ea870b5c567a3cb1eb1cLinux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < 656ff69ef235699035e57d9e1ae417e62a38aa7fLinux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < 136de17f38630307991c59aa7080012a99451783Linux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < c312b750bb5ac3348cfc85dab25e90937bd4d251Linux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < 58fd6cbc8541216af1d7ed272ea7ac2b66d50fd8Linux 2.6.25Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99284Nonenet: skbuff: propagate shared-frag marker in skb_zerocopy()
CVE-2026-99283Nonenetfilter: conntrack: tcp: use UNACK timeout for non-closing RST packets
CVE-2026-99272Nonesmb: client: validate the data area in SMB2_read()
CVE-2026-99271NoneALSA: line6: Clear prev_fbuf on capture buffer release
CVE-2026-99273Noneksmbd: reserve space for the UTF-16 terminator in stream info
CVE-2026-99275Nonesmb: client: reject short SESSION_SETUP responses