CVE-2026-72120

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 rcu list annotations and operations

sashiko-bot remarked the missing use of list_add_rcu() in bcm_[rx|tx]_setup() to have a proper initialized bcm_op structure when bcm_proc_show() traverses the bcm_op's under rcu_read_lock().

To cover all initial settings of the bcm_op's the list_add_rcu() calls are moved to the end of the setup code.

While at it, also fix the mirroring removal side: bcm_release() called bcm_remove_op() - which frees the op via call_rcu() - on ops that were still linked in bo->tx_ops/bo->rx_ops, without list_del_rcu() first. Unlink each op with list_del_rcu() before handing it to bcm_remove_op(), matching the existing pattern in bcm_delete_tx_op()/bcm_delete_rx_op().

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 17, 2026

Advisory Details (8)

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

can: bcm: add missing rcu list annotations and operations - kernel/git/stable/linux.git - Linux kernel stable tree

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

can: bcm: add missing rcu list annotations and operations - kernel/git/stable/linux.git - Linux kernel stable tree

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

can: bcm: add missing rcu list annotations and operations - kernel/git/stable/linux.git - Linux kernel stable tree

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

can: bcm: add missing rcu list annotations and operations - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8e1c7257c81577130f5ce90f69b2a2c3ce63f957
generic

can: bcm: add missing rcu list annotations and operations - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8357255e56dc1aaa437e3c53ee9385de984e0d57
generic

can: bcm: add missing rcu list annotations and operations - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7b2c3eabc4dafc062a25e10711154f2107526a78
generic

can: bcm: add missing rcu list annotations and operations - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4e22e8b505f877573bbdfdbcb680babad9b2f7a1
generic

can: bcm: add missing rcu list annotations and operations - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/30f7bb922cb7e7f072a56c7cb7a5efccd2ceca1d

Vendor Advisories for CVE-2026-72120(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 31× in last 7d / 31× 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-20 22:56 UTCEPSS rescore
  2. 2026-08-20 22:12 UTCGHSA enrichment
  3. 2026-08-20 11:13 UTCGHSA enrichment
  4. 2026-08-20 00:14 UTCEG score recompute
  5. 2026-08-20 00:14 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 13:15 UTCGHSA enrichment
  8. 2026-08-19 02:16 UTCGHSA enrichment
  9. 2026-08-18 15:17 UTCEG score recompute
  10. 2026-08-18 15:17 UTCGHSA enrichment
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 04:18 UTCGHSA enrichment
  14. 2026-08-17 17:18 UTCEG score recompute
  15. 2026-08-17 17:18 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 06:19 UTCEG score recompute
  18. 2026-08-17 06:18 UTCGHSA enrichment
  19. 2026-08-17 06:00 UTCEG score recompute▲ 7.80
  20. 2026-08-17 06:00 UTCGHSA enrichment
  21. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  22. 2026-08-17 05:33 UTCEG score recompute
  23. 2026-08-17 05:33 UTCGHSA enrichment
  24. 2026-08-17 05:24 UTCMITRE cvelistV5
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 6 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 02:15 UTCEPSS rescore
  3. 2026-08-15 06:43 UTCGHSA enrichment
  4. 2026-08-15 06:23 UTCNVD update
  5. 2026-08-15 06:12 UTCEG score recompute
  6. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72120?
CVE-2026-72120 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: can: bcm: add missing rcu list annotations and operations sashiko-bot remarked the missing use of listaddrcu() in bcm[rx|tx]setup() to have a proper initialized bcm_op structure when bcmprocshow() traverses the bcmop's under…
When was CVE-2026-72120 disclosed?
CVE-2026-72120 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72120 actively exploited?
CVE-2026-72120 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-72120?
CVE-2026-72120 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-72120?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72120, 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-72120

Explore →

Is Your Infrastructure Affected by CVE-2026-72120?

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

Start Free Scan →Browse All CVEs