Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2026-72116

can: bcm: fix stale rx/tx ops after device removal

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101, and 2 more
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

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.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  3. Record last updated

Affected versions

  • Linux 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 Linux

    2.6.25

  • KernelLinux

    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

References 8

git.kernel.org