CVE-2026-72113: Linux Vulnerability (CVSS 7.8)

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.

Metrics

CVSS 3.1

7.8/10

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

EPSS Probability

0.16%

6.0th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

Vendor	Product	Versions
Linux	Linux	>= ffd980f976e7fd666c2e61bf8ab35107efd11828, < bd5232663524e94cc5aad861dca11e3db8e2ab6f; >= ffd980f976e7fd666c2e61bf8ab35107efd11828, < ee8b36d0faca08f35b889b6e9aa850695e5b8ba9; >= ffd980f976e7fd666c2e61bf8ab35107efd11828, < dcaee869913c7210cd47ed0a8f27349d7bdcdb7b; >= ffd980f976e7fd666c2e61bf8ab35107efd11828, < 84aa4807816e405c1bf87114fc63e06d244281ef; >= ffd980f976e7fd666c2e61bf8ab35107efd11828, < 633bda66fbf309f5de5e1ad6defe8e6b1d77a20f; >= ffd980f976e7fd666c2e61bf8ab35107efd11828, < b024c21c9066f6957b7d4a8f2037e4b000c5e041; >= ffd980f976e7fd666c2e61bf8ab35107efd11828, < 04d23061bbf18d5d81022eb21e9d32e99d24468d; >= ffd980f976e7fd666c2e61bf8ab35107efd11828, < d59948293ea34b6337ce2b5febab8510de70048c
Linux	Linux	2.6.25

References

Timeline

Published: Aug 15, 2026
Last Modified: Aug 19, 2026
Status: Received

Frequently Asked Questions

What is CVE-2026-72113?

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.

How severe is CVE-2026-72113?

CVE-2026-72113 has a CVSS score of 7.8/10 (HIGH severity). The EPSS model estimates a 0.16% probability of exploitation in the next 30 days.

How do I fix CVE-2026-72113?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →