Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-72122: can: bcm: fix lockless bound/ifindex race and silent RX_SETUP failure

Noroxi assessment

Priority: Monitor (action score 29/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.16% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0f6f9f95294b4cbb26ba02209e893e3bd91237c3, 35f0ac19efb1a3f6c5e12c00e475a9ec2d9c3a6d, 6bcc5cd247c2934373bc2a1cdf8bf12321169543.

Low priority for now. Upgrade to Linux Linux 0f6f9f95294b4cbb26ba02209e893e3bd91237c3, 35f0ac19efb1a3f6c5e12c00e475a9ec2d9c3a6d, 6bcc5cd247c2934373bc2a1cdf8bf12321169543 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 lockless bound/ifindex race and silent RX_SETUP failure bcm_sendmsg() reads bo->ifindex and checks bo->bound before taking lock_sock(), while bcm_notify(), bcm_connect() and bcm_release() all mutate both fields under that same lock. Because the lockless reads and the locked writes are unordered with respect to each other, a racing bcm_notify() (device unregister) or bcm_connect() (concurrent bind on another thread sharing the socket) can make bcm_sendmsg() observe an inconsistent combination, e.g. a stale bound=1 together with the now-cleared ifindex=0, silently turning a socket bound to a specific CAN interface into one that also matches "any" interface. Keep the lockless bo->bound check purely as a fast-path reject, and move the ifindex read (and a bo->bound re-check) into the locked section, where every writer already serializes. This removes the possibility of observing the two fields torn against each other, rather than trying to fix it with more READ_ONCE()/WRITE_ONCE() pairs on two independently updated fields. Annotate the now-purely-lockless bo->bound accesses consistently across all its write sites. Also fix bcm_rx_setup() silently returning success when the target device disappears concurrently instead of reporting -ENODEV, so a broken RX op is no longer left registered as if it had succeeded.

HighCVSS 7.3 · v3.1—No exploit Fix available
Published
Aug 15, 2026
Updated
Oct 16, 2026
EPSS
0.1% · 5th percentile
CWE
—

Report tools

JSON

Action score

29

Monitor

Low priority for now.

CVSS
29 / 40 · 7.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.3
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-72122

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 9e60c586faeaed80d55ab8ce2a4b8e56133bc395affected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before ffa80a2af27c97453861a5128e537214a31cd18aaffected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before 6bcc5cd247c2934373bc2a1cdf8bf12321169543affected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before 0f6f9f95294b4cbb26ba02209e893e3bd91237c3affected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before b70f1a15533afeeec5d07f20bec3f3867ab1c7b6affected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before 35f0ac19efb1a3f6c5e12c00e475a9ec2d9c3a6daffected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before b9c6ac6fb4e01b34575816066e5d3890a57b3c86affected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before d9b091d9d22fee81ec53fb55d2032951993ceadbaffected · 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.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-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-72120Aug 15, 2026 · can: bcm: add missing rcu list annotations and operations
    31Monitor
  • ← EarlierCVE-2026-72121Aug 15, 2026 · can: bcm: add locking when updating filter and timer values
    35Monitor
  • Later →CVE-2026-72123Aug 15, 2026 · can: bcm: defer rx_op deallocation to workqueue to fix thrtimer UAF
    31Monitor

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 Linux0f6f9f95294b4cbb26ba02209e893e3bd91237c3Vendor (CNA)
Linux Linux35f0ac19efb1a3f6c5e12c00e475a9ec2d9c3a6dVendor (CNA)
Linux Linux6bcc5cd247c2934373bc2a1cdf8bf12321169543Vendor (CNA)
Linux Linux9e60c586faeaed80d55ab8ce2a4b8e56133bc395Vendor (CNA)
Linux Linuxb70f1a15533afeeec5d07f20bec3f3867ab1c7b6Vendor (CNA)
Linux Linuxb9c6ac6fb4e01b34575816066e5d3890a57b3c86Vendor (CNA)
Linux Linuxd9b091d9d22fee81ec53fb55d2032951993ceadbVendor (CNA)
Linux Linuxffa80a2af27c97453861a5128e537214a31cd18aVendor (CNA)
debian:linux6.1.180-1 · 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

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
low · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
Low

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

nvd-secondary

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