CVE-2026-68210

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 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:

media: stm32: dcmi: unregister notifier on probe failure

dcmi_graph_init() registers the async notifier before dcmi_probe() toggles the reset line. If reset_control_assert() or reset_control_deassert() fails afterwards, probe returns through err_cleanup and the driver core will not call dcmi_remove().

Unregister the notifier before cleaning it up on that error path, matching the successful remove path and the V4L2 async notifier lifetime rules.

[hverkuil: added Fixes tag]

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
7%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 19, 2026

Advisory Details (5)

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

media: stm32: dcmi: unregister notifier on probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/931abe1deb65b919d23fa203d7f6d6fbd4fccd8e
generic

media: stm32: dcmi: unregister notifier on probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6c6f22b7e6cbc4e8c1e359fc9b190419391c3db7
generic

media: stm32: dcmi: unregister notifier on probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

media: stm32: dcmi: unregister notifier on probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/37ff63c5d7119cbc5c6bacdcc658add6008a8e1f
generic

media: stm32: dcmi: unregister notifier on probe failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/084973ebd67b28f0945c5d45408f86c58b540110

Vendor Advisories for CVE-2026-68210(2)

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 37× in last 7d / 43× 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 05:47 UTCGHSA enrichment
  2. 2026-08-19 17:25 UTCEG score recompute
  3. 2026-08-19 17:25 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 16:55 UTCEG score recompute
  6. 2026-08-19 16:55 UTCGHSA enrichment
  7. 2026-08-19 08:26 UTCGHSA enrichment
  8. 2026-08-18 20:05 UTCEG score recompute
  9. 2026-08-18 20:05 UTCGHSA enrichment
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 07:44 UTCGHSA enrichment
  13. 2026-08-17 19:20 UTCEG score recompute
  14. 2026-08-17 19:20 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 05:38 UTCEG score recompute
  17. 2026-08-17 05:38 UTCGHSA enrichment
  18. 2026-08-17 05:09 UTCEG score recompute
  19. 2026-08-17 05:09 UTCGHSA enrichment
  20. 2026-08-17 01:35 UTCEG score recompute
  21. 2026-08-17 01:35 UTCGHSA enrichment
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 13:13 UTCEG score recompute
  24. 2026-08-16 13:13 UTCGHSA enrichment
  25. 2026-08-16 00:53 UTCGHSA enrichment
Show 18 more
  1. 2026-08-15 12:32 UTCEG score recompute
  2. 2026-08-15 12:32 UTCGHSA enrichment
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-15 00:11 UTCGHSA enrichment
  5. 2026-08-14 11:50 UTCEG score recompute
  6. 2026-08-14 11:50 UTCGHSA enrichment
  7. 2026-08-13 23:29 UTCEG score recompute
  8. 2026-08-13 23:29 UTCGHSA enrichment
  9. 2026-08-13 22:44 UTCEG score recompute▲ 7.80
  10. 2026-08-13 22:44 UTCGHSA enrichment
  11. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-13 08:06 UTCEG score recompute
  14. 2026-08-13 08:06 UTCGHSA enrichment
  15. 2026-08-12 13:51 UTCEPSS rescore
  16. 2026-08-10 13:24 UTCNVD update
  17. 2026-08-10 12:20 UTCEG score recompute
  18. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68210?
CVE-2026-68210 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: media: stm32: dcmi: unregister notifier on probe failure dcmigraphinit() registers the async notifier before dcmi_probe() toggles the reset line. If resetcontrolassert() or resetcontroldeassert() fails afterwards, probe returns…
When was CVE-2026-68210 disclosed?
CVE-2026-68210 was first published in the National Vulnerability Database on August 10, 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-68210 actively exploited?
CVE-2026-68210 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 92.7% of all scored CVEs.
What is the CVSS score of CVE-2026-68210?
CVE-2026-68210 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68210?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68210, 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-68210

Explore →

Is Your Infrastructure Affected by CVE-2026-68210?

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

Start Free Scan →Browse All CVEs