---
cve: "CVE-2026-72115"
severity: "HIGH"
cvss: 8.1
epss: "30%"
vendor: "Linux"
kev: false
exploited: false
published: "2026-08-15 06:21:25"
tags: [cve, security, high]
source: tsecurity.de CVE-Dossier
exported: "2026-09-10T04:22:24+02:00"
---

# CVE-2026-72115

> 8.1 HIGH

## Beschreibung

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

## CVSS-Vektor

```
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
```

| Metrik | Wert | Bewertung |
|---|---|---|
| AV Angriffsvektor | Benachbart | warn |
| AC Komplexität | Gering | bad |
| PR Privilegien | Keine | bad |
| UI Interaktion | Keine | bad |
| S Scope | Unverändert | good |
| C Vertraulichkeit | Hoch | bad |
| I Integrität | Hoch | bad |
| A Verfügbarkeit | Keine | good |

## Patch verfügbar (OSV)

- Kernel ≥ 5.10.265
- Kernel ≥ 5.15.216
- Kernel ≥ 6.1.183
- Kernel ≥ 6.6.148
- Kernel ≥ 6.12.101
- Kernel ≥ 6.18.42
- Kernel ≥ 7.1.5

## Referenzen

- <https://git.kernel.org/stable/c/f147f48837cb1426521f5b3c3b3134c71128a25d>
- <https://git.kernel.org/stable/c/57cf104da4cf450ae9c16801a3164604b801d2cc>
- <https://git.kernel.org/stable/c/03dfe347c398fa41a7e30e8dc538f12568c183e6>
- <https://git.kernel.org/stable/c/18b45251e74e35668f0dd0c470549384ae191ecf>
- <https://git.kernel.org/stable/c/3ff8c24b421070a2db99a5cdb86edc9ff339418e>
- <https://git.kernel.org/stable/c/eca8b44d51fc6ab61022258ec968e55e3073b79e>
- <https://git.kernel.org/stable/c/b6317022b685a430a3ae420456716e3c0c02ef4b>
- <https://git.kernel.org/stable/c/2f5976f54a04e9f18b25283036ac3136be453b17>

---
_Exportiert aus dem [tsecurity.de CVE-Dossier](https://tsecurity.de/cve?cve=CVE-2026-72115) · Datenquellen: EUVD (ENISA), NVD, OSV, CISA KEV, FIRST EPSS, Exploit-DB, BSI BITS_