Description
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: 2026-08-15
Score: 7.1 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

This CVE describes a resource management weakness (CWE‑772) in the Linux kernel’s CAN bus BCM driver. After a CAN device is removed, a stale rx operation could skip re‑registration, and a stale tx operation could leave a cyclic hrtimer active. The runaway timer may repeatedly invoke the timeout handler, consuming CPU cycles and potentially injecting data into a later reused interface index. The bug also silently disables frame delivery for updated filters, disrupting normal CAN communication. The fix re‑registers the RX operation when necessary and cancels the runaway timer during device removal, preventing denial of service through resource exhaustion or unintended message injection.

Affected Systems

Affected systems are all Linux kernel releases that contain the bcm CAN driver and have not yet applied the patch. This includes any distribution kernel version preceding the commit that implements the described changes. All systems using the bcm driver for CAN communication are potentially impacted.

Risk and Exploitability

The CVSS score is 7.1, indicating a moderate to high severity, while the EPSS score is less than 1%, suggesting a low probability of current exploitation. The vulnerability is not listed in the CISA KEV catalog. It requires local or privileged interaction, specifically removal of a CAN device that triggers stale rx or tx operations. The likely attack vector is local or privilege‑elevated, through triggering device removal and inducing a runaway timer or data injection into a reused interface index. Broad exploitation is unlikely without kernel access, but the risk of service disruption remains until the patch is applied.

Generated by OpenCVE AI on August 18, 2026 at 04:45 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the kernel to a version that includes the bcm CAN driver patch that re‑registers RX operations and cancels hrtimers on device removal.
  • If an upgrade is not yet possible, disable or unload the bcm CAN driver from the kernel to prevent stale operations until the kernel can be patched.
  • Monitor kernel logs for repeated "bcm_tx_timeout_handler" or "hrtimer" entries and verify that hrtimers are not repeatedly scheduled.

Generated by OpenCVE AI on August 18, 2026 at 04:45 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4745-1 linux-6.12 security update
History

Wed, 19 Aug 2026 16:45:00 +0000


Tue, 18 Aug 2026 03:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-399

Tue, 18 Aug 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-772
References
Metrics threat_severity

None

threat_severity

Moderate


Mon, 17 Aug 2026 18:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-399

Mon, 17 Aug 2026 08:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-399

Mon, 17 Aug 2026 06:00:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H'}


Sat, 15 Aug 2026 20:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-399

Sat, 15 Aug 2026 06:00:00 +0000

Type Values Removed Values Added
Description 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.
Title can: bcm: fix stale rx/tx ops after device removal
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-19T16:36:05.976Z

Reserved: 2026-08-09T03:40:39.906Z

Link: CVE-2026-72116

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-15T06:21:26.020

Modified: 2026-08-19T17:20:57.960

Link: CVE-2026-72116

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-08-15T00:00:00Z

Links: CVE-2026-72116 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-18T05:00:09Z

Weaknesses
  • CWE-772

    Missing Release of Resource after Effective Lifetime