Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-72117can: bcm: fix data race on rx_stamp/rx_ifindex in bcm_rx_handler()

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < b64f60c468d149aca22ea56bb842b9730215aaa5
    • affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < c8a5d7cb095d3b12bd9dcf752d6ca0ff50872ac5
    • affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < 4b97410f4bba18d2ee2784c8e089104f387bc27c
    • affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < 5f246b96ab47523ec9b8ea870b5c567a3cb1eb1c
    • affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < 656ff69ef235699035e57d9e1ae417e62a38aa7f
    • affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < 136de17f38630307991c59aa7080012a99451783
    • affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < c312b750bb5ac3348cfc85dab25e90937bd4d251
    • affected ffd980f976e7fd666c2e61bf8ab35107efd11828 – < 58fd6cbc8541216af1d7ed272ea7ac2b66d50fd8
  • Linux · Linux

    • affected 2.6.25
    • unaffected < 2.6.25
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-72117 badge
[![CVE-2026-72117](https://cveledger.app/badge/CVE-2026-72117.svg)](https://cveledger.app/cve/CVE-2026-72117)

Record last updated .