CVE-2026-72113

can: bcm: add missing device refcount for CAN filter removal

HIGH
7.8
CVSS Score
Published: August 15, 2026 at 05:52 AM UTC
Updated: October 16, 2026 at 07:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: can: bcm: add missing device refcount for CAN filter removal sashiko-bot remarked a problem with a concurrent device unregistration in isotp.c which also is present in the bcm.c code. A former fix for raw.c commit c275a176e4b6 ("can: raw: add missing refcount for memory leak fix") introduced a netdevice_tracker which solves the issue for bcm.c too. bcm_release(), bcm_delete_rx_op() and bcm_notifier() relied on dev_get_by_index(ifindex) to re-find the device for an rx_op before unregistering its filter. If a concurrent NETDEV_UNREGISTER has already unlisted the device from the ifindex table, that lookup fails and can_rx_unregister() is silently skipped, leaving a stale CAN filter pointing at the soon-to-be-freed bcm_op/socket. Hold a netdev_hold()/netdev_put() tracked reference on op->rx_reg_dev from the moment the rx filter is registered in bcm_rx_setup() until it is unregistered in bcm_rx_unreg(), and use that reference directly in bcm_release() and bcm_delete_rx_op() instead of re-looking the device up by ifindex.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.25ffd980f976e7fd666c2e61bf8ab35107efd11828
Vendor states this is fixed in 04d23061bbf18d5d81022eb21e9d32e99d24468d (fixed)
Vendor states this is fixed in 633bda66fbf309f5de5e1ad6defe8e6b1d77a20f (fixed)
Vendor states this is fixed in 84aa4807816e405c1bf87114fc63e06d244281ef (fixed)
Vendor states this is fixed in b024c21c9066f6957b7d4a8f2037e4b000c5e041 (fixed)
Vendor states this is fixed in bd5232663524e94cc5aad861dca11e3db8e2ab6f (fixed)
Vendor states this is fixed in d59948293ea34b6337ce2b5febab8510de70048c (fixed)
Vendor states this is fixed in dcaee869913c7210cd47ed0a8f27349d7bdcdb7b (fixed)
Vendor states this is fixed in ee8b36d0faca08f35b889b6e9aa850695e5b8ba9 (fixed)
Vendor states this is fixed in 2.6.25 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card