High

CVE-2026-72116 — can: bcm: fix stale rx/tx ops after device removal

In the Linux kernel, the following vulnerability has been resolved: can: bcm: fix stale rx/tx ops after device removal RX: an RX_SETUP update(!) for an existing op skipped can_rx_register() unconditionally, even when a concurrent NETDEV_UNREGISTER had already torn down its registration (op->rx_reg_dev == NULL). This silently did not re-enable frame delivery for that updated filter. bcm_rx_setup() now re-registers in that case, while leaving rx_ops with ifindex = 0 (all CAN devices) which never carry a tracked rx_reg_dev registered as-is. TX: bcm_notify() only handled bo->rx_ops on NETDEV_UNREGISTER, leaving tx_ops with an active cyclic transmission re-arming its hrtimer indefinitely to execute bcm_tx_timeout_handler(). Cancelling the hrtimer prevents the runaway timer and any injection into a later reused ifindex, since nothing else calls bcm_can_tx() for the op until an explicit TX_SETUP update re-arms it. Unlike bcm_rx_unreg(), which clears the tracked rx_reg_dev for rx_ops, the ifindex is intentionally left unchanged for tx_ops. bcm_tx_setup() always rejects ifindex 0, so clearing it would strand the op: neither a later TX_SETUP (bcm_find_op()) nor TX_DELETE (bcm_delete_tx_op()) could ever find it again, since both require an exact ifindex match.

Published Aug 15, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

—

No EPSS score.

Affects

Linux

CVSS base

7.1

High · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	≥ ffd980f976e7fd666c2e61bf8ab35107efd11828 and < d30a36066ed3abefb72ae18901f71841ba18b350≥ ffd980f976e7fd666c2e61bf8ab35107efd11828 and < ca829677ffa2de5d79e06366e19ac1e4f5cc78dd≥ ffd980f976e7fd666c2e61bf8ab35107efd11828 and < 9517d8fb0b191398d35b9b7f8c719c1cc7761cb1≥ ffd980f976e7fd666c2e61bf8ab35107efd11828 and < 60d8a7942f4ed2d975207aaeba1adb576707e53d≥ ffd980f976e7fd666c2e61bf8ab35107efd11828 and < f749e4564952d60e96930c09f2be99955d07c22e≥ ffd980f976e7fd666c2e61bf8ab35107efd11828 and < 6be3e1fedf03eab36a2c09d755d1171287b2014b≥ ffd980f976e7fd666c2e61bf8ab35107efd11828 and < b31d0933509c5a35c0be5736a2ce8df0d1bf112c≥ ffd980f976e7fd666c2e61bf8ab35107efd11828 and < 3b762c0d950383ab7a002686c9136b9aa55d2d70 and 1 more version 2.6.25	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Local

Attack complexity

Low

Privileges required

Low

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
7.1	CVSS 3.1	High	1.8	5.2	416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database
7.1	CVSS 3.1	High	—	—	Linux via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67)

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.

endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

2026
Affected products added · linux/linux
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 15, 2026
CVSS changed · 7.1
Oct 15, 2026 · NIST National Vulnerability Database
Source status changed · → Received
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Aug 15, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

8 on the record

git.kernel.org/stable/c/60d8a7942f4ed2d975207aaeba1adb576707e53d
NIST National Vulnerability Database
git.kernel.org/stable/c/6be3e1fedf03eab36a2c09d755d1171287b2014b
NIST National Vulnerability Database
git.kernel.org/stable/c/ca829677ffa2de5d79e06366e19ac1e4f5cc78dd
NIST National Vulnerability Database
git.kernel.org/stable/c/3b762c0d950383ab7a002686c9136b9aa55d2d70
NIST National Vulnerability Database
git.kernel.org/stable/c/d30a36066ed3abefb72ae18901f71841ba18b350
NIST National Vulnerability Database
git.kernel.org/stable/c/9517d8fb0b191398d35b9b7f8c719c1cc7761cb1
NIST National Vulnerability Database
git.kernel.org/stable/c/b31d0933509c5a35c0be5736a2ce8df0d1bf112c
NIST National Vulnerability Database
git.kernel.org/stable/c/f749e4564952d60e96930c09f2be99955d07c22e
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 11h
Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 11h
Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No FIRST EPSS score.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-72116 is "can: bcm: fix stale rx/tx ops after device removal", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.1 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.