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

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

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: total

Summary

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().

Timeline

  1. CVE published
  2. CISA SSVC assessment

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

  3. Record last updated

Affected versions

  • Linux Linux

    From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in f147f48837cb1426521f5b3c3b3134c71128a25d; From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in 57cf104da4cf450ae9c16801a3164604b801d2cc; From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in 03dfe347c398fa41a7e30e8dc538f12568c183e6; From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in 18b45251e74e35668f0dd0c470549384ae191ecf; From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in 3ff8c24b421070a2db99a5cdb86edc9ff339418e; From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in eca8b44d51fc6ab61022258ec968e55e3073b79e; From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in b6317022b685a430a3ae420456716e3c0c02ef4b; From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in 2f5976f54a04e9f18b25283036ac3136be453b17

  • 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