Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Fixed version: Linux Linux 136de17f38630307991c59aa7080012a99451783, 4b97410f4bba18d2ee2784c8e089104f387bc27c, 58fd6cbc8541216af1d7ed272ea7ac2b66d50fd8.

Low priority for now. Upgrade to Linux Linux 136de17f38630307991c59aa7080012a99451783, 4b97410f4bba18d2ee2784c8e089104f387bc27c, 58fd6cbc8541216af1d7ed272ea7ac2b66d50fd8 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Aug 15, 2026
Updated
Nov 6, 2026
EPSS
0.2% · 12th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-72117

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.25affected
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before b64f60c468d149aca22ea56bb842b9730215aaa5affected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before c8a5d7cb095d3b12bd9dcf752d6ca0ff50872ac5affected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before 4b97410f4bba18d2ee2784c8e089104f387bc27caffected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before 5f246b96ab47523ec9b8ea870b5c567a3cb1eb1caffected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before 656ff69ef235699035e57d9e1ae417e62a38aa7faffected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before 136de17f38630307991c59aa7080012a99451783affected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before c312b750bb5ac3348cfc85dab25e90937bd4d251affected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before 58fd6cbc8541216af1d7ed272ea7ac2b66d50fd8affected · git
    • before 2.6.25not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.187-16.1.187-1
Debian:12linux-6.12before 6.12.101-1~deb12u16.12.101-1~deb12u1
Debian:13linuxbefore 6.12.101-16.12.101-1
Debian:14linuxbefore 7.1.5-17.1.5-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-72115Aug 15, 2026 · can: bcm: track a single source interface for ANYDEV timeout/throttle ops
    32Monitor
  • ← EarlierCVE-2026-72116Aug 15, 2026 · can: bcm: fix stale rx/tx ops after device removal
    28Monitor
  • Later →CVE-2026-72118Aug 15, 2026 · can: bcm: fix CAN frame rx/tx statistics
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux136de17f38630307991c59aa7080012a99451783Vendor (CNA)
Linux Linux4b97410f4bba18d2ee2784c8e089104f387bc27cVendor (CNA)
Linux Linux58fd6cbc8541216af1d7ed272ea7ac2b66d50fd8Vendor (CNA)
Linux Linux5f246b96ab47523ec9b8ea870b5c567a3cb1eb1cVendor (CNA)
Linux Linux656ff69ef235699035e57d9e1ae417e62a38aa7fVendor (CNA)
Linux Linuxb64f60c468d149aca22ea56bb842b9730215aaa5Vendor (CNA)
Linux Linuxc312b750bb5ac3348cfc85dab25e90937bd4d251Vendor (CNA)
Linux Linuxc8a5d7cb095d3b12bd9dcf752d6ca0ff50872ac5Vendor (CNA)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.101-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records