---
id: CVE-2026-72115
title: 'can: bcm: track a single source interface for ANYDEV timeout/throttle ops'
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…
severity: high
cvss: 8.1
cvssVector: 'CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'
cvssSource: cna
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 <
    f147f48837cb1426521f5b3c3b3134c71128a25d
  - >-
    Linux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 <
    57cf104da4cf450ae9c16801a3164604b801d2cc
  - >-
    Linux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 <
    03dfe347c398fa41a7e30e8dc538f12568c183e6
  - >-
    Linux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 <
    18b45251e74e35668f0dd0c470549384ae191ecf
  - >-
    Linux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 <
    3ff8c24b421070a2db99a5cdb86edc9ff339418e
  - >-
    Linux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 <
    eca8b44d51fc6ab61022258ec968e55e3073b79e
  - >-
    Linux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 <
    b6317022b685a430a3ae420456716e3c0c02ef4b
  - >-
    Linux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 <
    2f5976f54a04e9f18b25283036ac3136be453b17
  - Linux 2.6.25
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: total
  timestamp: '2026-10-16T18:41:50.278770Z'
published: '2026-08-15'
updated: '2026-10-16'
sourceUpdated: '2026-10-16T18:44:56.703Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-72115'
references:
  - url: 'https://git.kernel.org/stable/c/f147f48837cb1426521f5b3c3b3134c71128a25d'
  - url: 'https://git.kernel.org/stable/c/57cf104da4cf450ae9c16801a3164604b801d2cc'
  - url: 'https://git.kernel.org/stable/c/03dfe347c398fa41a7e30e8dc538f12568c183e6'
  - url: 'https://git.kernel.org/stable/c/18b45251e74e35668f0dd0c470549384ae191ecf'
  - url: 'https://git.kernel.org/stable/c/3ff8c24b421070a2db99a5cdb86edc9ff339418e'
  - url: 'https://git.kernel.org/stable/c/eca8b44d51fc6ab61022258ec968e55e3073b79e'
  - url: 'https://git.kernel.org/stable/c/b6317022b685a430a3ae420456716e3c0c02ef4b'
  - url: 'https://git.kernel.org/stable/c/2f5976f54a04e9f18b25283036ac3136be453b17'
tags:
  - cve.org
epss: 0.00303
epssPercentile: 0.21515
ingestedAt: '2026-10-16T19:46:24.431Z'
---

## Overview

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

## Affected

- `Linux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < f147f48837cb1426521f5b3c3b3134c71128a25d`
- `Linux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < 57cf104da4cf450ae9c16801a3164604b801d2cc`
- `Linux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < 03dfe347c398fa41a7e30e8dc538f12568c183e6`
- `Linux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < 18b45251e74e35668f0dd0c470549384ae191ecf`
- `Linux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < 3ff8c24b421070a2db99a5cdb86edc9ff339418e`
- `Linux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < eca8b44d51fc6ab61022258ec968e55e3073b79e`
- `Linux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < b6317022b685a430a3ae420456716e3c0c02ef4b`
- `Linux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < 2f5976f54a04e9f18b25283036ac3136be453b17`
- `Linux 2.6.25`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.