Answer in brief
CVE-2026-72113 records a Unknown severity vulnerability in can: bcm: add missing device refcount for CAN filter removal. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <84aa4807816e405c1bf87114fc63e06d244281ef || >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <633bda66fbf309f5de5e1ad6defe8e6b1d77a20f || >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <b024c21c9066f6957b7d4a8f2037e4b000c5e041 || >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <04d23061bbf18d5d81022eb21e9d32e99d24468d || >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <d59948293ea34b6337ce2b5febab8510de70048c | 84aa4807816e405c1bf87114fc63e06d244281ef, 633bda66fbf309f5de5e1ad6defe8e6b1d77a20f, b024c21c9066f6957b7d4a8f2037e4b000c5e041, 04d23061bbf18d5d81022eb21e9d32e99d24468d, d59948293ea34b6337ce2b5febab8510de70048c |
| Linux/Linuxgeneric | 2.6.25 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-72113 records a Unknown severity vulnerability in can: bcm: add missing device refcount for CAN filter removal. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <84aa4807816e405c1bf87114fc63e06d244281ef || >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <633bda66fbf309f5de5e1ad6defe8e6b1d77a20f || >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <b024c21c9066f6957b7d4a8f2037e4b000c5e041 || >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <04d23061bbf18d5d81022eb21e9d32e99d24468d || >=ffd980f976e7fd666c2e61bf8ab35107efd11828 <d59948293ea34b6337ce2b5febab8510de70048c | 84aa4807816e405c1bf87114fc63e06d244281ef, 633bda66fbf309f5de5e1ad6defe8e6b1d77a20f, b024c21c9066f6957b7d4a8f2037e4b000c5e041, 04d23061bbf18d5d81022eb21e9d32e99d24468d, d59948293ea34b6337ce2b5febab8510de70048c |
| Linux/Linuxgeneric | 2.6.25 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.