can: bcm: track a single source interface for ANYDEV timeout/throttle ops
Summary
| CVE | CVE-2026-72115 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-15 06:21:25 UTC |
| Updated | 2026-08-17 06:18:10 UTC |
| Description | 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(). |
Risk And Classification
Primary CVSS: v3.1 8.1 HIGH from 416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS: 0.002810000 probability, percentile 0.206750000 (date 2026-08-19)
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | Secondary | 8.1 | HIGH | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| 3.1 | CNA | DECLARED | 8.1 | HIGH | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
CVSS v3.1 Breakdown
Attack Vector
AdjacentAttack Complexity
LowPrivileges Required
NoneUser Interaction
NoneScope
UnchangedConfidentiality
HighIntegrity
HighAvailability
NoneCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected ffd980f976e7fd666c2e61bf8ab35107efd11828 f147f48837cb1426521f5b3c3b3134c71128a25d git | Not specified |
| CNA | Linux | Linux | affected ffd980f976e7fd666c2e61bf8ab35107efd11828 57cf104da4cf450ae9c16801a3164604b801d2cc git | Not specified |
| CNA | Linux | Linux | affected ffd980f976e7fd666c2e61bf8ab35107efd11828 03dfe347c398fa41a7e30e8dc538f12568c183e6 git | Not specified |
| CNA | Linux | Linux | affected ffd980f976e7fd666c2e61bf8ab35107efd11828 18b45251e74e35668f0dd0c470549384ae191ecf git | Not specified |
| CNA | Linux | Linux | affected ffd980f976e7fd666c2e61bf8ab35107efd11828 3ff8c24b421070a2db99a5cdb86edc9ff339418e git | Not specified |
| CNA | Linux | Linux | affected ffd980f976e7fd666c2e61bf8ab35107efd11828 eca8b44d51fc6ab61022258ec968e55e3073b79e git | Not specified |
| CNA | Linux | Linux | affected ffd980f976e7fd666c2e61bf8ab35107efd11828 b6317022b685a430a3ae420456716e3c0c02ef4b git | Not specified |
| CNA | Linux | Linux | affected ffd980f976e7fd666c2e61bf8ab35107efd11828 2f5976f54a04e9f18b25283036ac3136be453b17 git | Not specified |
| CNA | Linux | Linux | affected 2.6.25 | Not specified |
| CNA | Linux | Linux | unaffected 2.6.25 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.10.265 5.10.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.216 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.183 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.148 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.101 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.42 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1.5 7.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/18b45251e74e35668f0dd0c470549384ae191ecf | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/b6317022b685a430a3ae420456716e3c0c02ef4b | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/57cf104da4cf450ae9c16801a3164604b801d2cc | https://git.kernel.org/stable/c/57cf104da4cf450ae9c16801a3164604b801d2cc | git.kernel.org | |
| git.kernel.org/stable/c/03dfe347c398fa41a7e30e8dc538f12568c183e6 | https://git.kernel.org/stable/c/03dfe347c398fa41a7e30e8dc538f12568c183e6 | git.kernel.org | |
| git.kernel.org/stable/c/2f5976f54a04e9f18b25283036ac3136be453b17 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/f147f48837cb1426521f5b3c3b3134c71128a25d | https://git.kernel.org/stable/c/f147f48837cb1426521f5b3c3b3134c71128a25d | git.kernel.org | |
| git.kernel.org/stable/c/3ff8c24b421070a2db99a5cdb86edc9ff339418e | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/eca8b44d51fc6ab61022258ec968e55e3073b79e | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.