Skip to content
Noroxi
CVE-2026-72115· NVD / CVE Program· CNA Linux

can: bcm: track a single source interface for ANYDEV timeout/throttle ops

Noroxi assessment

Priority: Monitor (action score 32/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.30% (FIRST EPSS).
  • Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 03dfe347c398fa41a7e30e8dc538f12568c183e6, 18b45251e74e35668f0dd0c470549384ae191ecf, 2f5976f54a04e9f18b25283036ac3136be453b17.

Low priority for now. Upgrade to Linux Linux 03dfe347c398fa41a7e30e8dc538f12568c183e6, 18b45251e74e35668f0dd0c470549384ae191ecf, 2f5976f54a04e9f18b25283036ac3136be453b17 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: track a single source interface for ANYDEV timeout/throttle ops An ANYDEV rx op (ifindex == 0) with an active RX timeout and/or throttle timer has no defined semantics when matching frames arrive from several interfaces: bcm_rx_handler() can run concurrently for the same op on different CPUs, racing hrtimer_cancel()/ bcm_rx_starttimer() against bcm_rx_timeout_handler() and causing spurious RX_TIMEOUT notifications and last_frames corruption. The same concurrency lets throttled multiplex frames from different interfaces clobber the single rx_ifindex/rx_stamp fields shared by the op. Add op->if_detected to track the first interface that delivers a matching frame while a timeout/throttle timer is configured, and reject frames from any other interface for that op. The claim is decided in bcm_rx_handler() before hrtimer_cancel() touches op->timer, so a rejected frame can never disturb the claimed interface's watchdog. RTR-mode ops are excluded via RX_RTR_FRAME, independent of kt_ival1/kt_ival2, since those may briefly hold a stale value from an earlier non-RTR configuration. The claim is released in bcm_notify() on NETDEV_UNREGISTER and in bcm_rx_setup() when SETTIMER reconfigures the timer values. A (re-)claim is only possible on CAN devices in NETREG_REGISTERED dev->reg_state to cover the release in bcm_notify() where reg_state becomes NETREG_UNREGISTERING until synchronize_net().

HighCVSS 8.1 · v3.1—No exploit Fix available
Published
Aug 15, 2026
Updated
Oct 16, 2026
EPSS
0.3% · 21th percentile
CWE
—

Report tools

JSON

Action score

32

Monitor

Low priority for now.

CVSS
32 / 40 · 8.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
8.1
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-72115

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 f147f48837cb1426521f5b3c3b3134c71128a25daffected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before 57cf104da4cf450ae9c16801a3164604b801d2ccaffected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before 03dfe347c398fa41a7e30e8dc538f12568c183e6affected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before 18b45251e74e35668f0dd0c470549384ae191ecfaffected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before 3ff8c24b421070a2db99a5cdb86edc9ff339418eaffected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before eca8b44d51fc6ab61022258ec968e55e3073b79eaffected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before b6317022b685a430a3ae420456716e3c0c02ef4baffected · git
    • ffd980f976e7fd666c2e61bf8ab35107efd11828 and later · before 2f5976f54a04e9f18b25283036ac3136be453b17affected · 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-72113Aug 15, 2026 · can: bcm: add missing device refcount for CAN filter removal
    31Monitor
  • ← EarlierCVE-2026-72114Aug 15, 2026 · can: bcm: validate frame length in bcm_rx_setup() for RTR replies
    31Monitor
  • Later →CVE-2026-72116Aug 15, 2026 · can: bcm: fix stale rx/tx ops after device removal
    28Monitor

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 Linux03dfe347c398fa41a7e30e8dc538f12568c183e6Vendor (CNA)
Linux Linux18b45251e74e35668f0dd0c470549384ae191ecfVendor (CNA)
Linux Linux2f5976f54a04e9f18b25283036ac3136be453b17Vendor (CNA)
Linux Linux3ff8c24b421070a2db99a5cdb86edc9ff339418eVendor (CNA)
Linux Linux57cf104da4cf450ae9c16801a3164604b801d2ccVendor (CNA)
Linux Linuxb6317022b685a430a3ae420456716e3c0c02ef4bVendor (CNA)
Linux Linuxeca8b44d51fc6ab61022258ec968e55e3073b79eVendor (CNA)
Linux Linuxf147f48837cb1426521f5b3c3b3134c71128a25dVendor (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

Attack conditions

  • Someone on the same network segment can trigger it.
  • No account or password is required.
  • 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
none
Attack vector
Adjacent
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
None

Weakness class (CWE)

—

CVSS vector

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

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