CVE-2026-72113

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 19, 2026

Advisory Details (5)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

can: bcm: add missing device refcount for CAN filter removal - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d59948293ea34b6337ce2b5febab8510de70048c
generic

can: bcm: add missing device refcount for CAN filter removal - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b024c21c9066f6957b7d4a8f2037e4b000c5e041
generic

can: bcm: add missing device refcount for CAN filter removal - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/84aa4807816e405c1bf87114fc63e06d244281ef
generic

can: bcm: add missing device refcount for CAN filter removal - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/633bda66fbf309f5de5e1ad6defe8e6b1d77a20f
generic

can: bcm: add missing device refcount for CAN filter removal - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/04d23061bbf18d5d81022eb21e9d32e99d24468d

Vendor Advisories for CVE-2026-72113(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 35× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 03:48 UTCEG score recompute
  2. 2026-08-21 03:48 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 16:25 UTCGHSA enrichment
  5. 2026-08-20 05:02 UTCGHSA enrichment
  6. 2026-08-19 17:39 UTCEG score recompute
  7. 2026-08-19 17:39 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 16:46 UTCEG score recompute
  10. 2026-08-19 16:46 UTCGHSA enrichment
  11. 2026-08-19 15:56 UTCGHSA enrichment
  12. 2026-08-19 04:29 UTCGHSA enrichment
  13. 2026-08-18 17:02 UTCEG score recompute
  14. 2026-08-18 17:02 UTCGHSA enrichment
  15. 2026-08-18 13:49 UTCEPSS rescore
  16. 2026-08-18 13:49 UTCEPSS rescore
  17. 2026-08-18 05:09 UTCGHSA enrichment
  18. 2026-08-17 17:45 UTCEG score recompute
  19. 2026-08-17 17:44 UTCGHSA enrichment
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-17 06:19 UTCEG score recompute
  22. 2026-08-17 06:19 UTCGHSA enrichment
  23. 2026-08-17 06:00 UTCEG score recompute▲ 7.80
  24. 2026-08-17 06:00 UTCGHSA enrichment
  25. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
Show 10 more
  1. 2026-08-17 05:33 UTCEG score recompute
  2. 2026-08-17 05:33 UTCGHSA enrichment
  3. 2026-08-17 05:25 UTCMITRE cvelistV5
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-16 14:56 UTCEPSS rescore
  6. 2026-08-16 02:15 UTCEPSS rescore
  7. 2026-08-15 06:43 UTCGHSA enrichment
  8. 2026-08-15 06:23 UTCNVD update
  9. 2026-08-15 06:12 UTCEG score recompute
  10. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72113?
CVE-2026-72113 is a high vulnerability published on August 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…
When was CVE-2026-72113 disclosed?
CVE-2026-72113 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72113 actively exploited?
CVE-2026-72113 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.9% of all scored CVEs.
What is the CVSS score of CVE-2026-72113?
CVE-2026-72113 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-72113?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72113, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-72113

Explore →

Is Your Infrastructure Affected by CVE-2026-72113?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs