CVE-2026-68206

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: v4l2-ctrls: validate HEVC active reference counts

HEVC slice parameters are shared stateless V4L2 controls, but the common validation path does not verify the active L0/L1 reference counts before driver-specific code consumes them.

The original report came from Cedrus, but the active count bounds are not Cedrus-specific. Validate them in the common HEVC slice control path so stateless HEVC drivers get the same basic guarantees as soon as the control is queued.

Do not reject ref_idx_l0/ref_idx_l1 entries here. Existing userspace may use out-of-range sentinel values such as 0xff for missing references, and some hardware can use that information for concealment. Keep this common check limited to the active reference counts.

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: v4l2-ctrls: validate HEVC active reference counts - kernel/git/stable/linux.git - Linux kernel stable tree

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

media: v4l2-ctrls: validate HEVC active reference counts - kernel/git/stable/linux.git - Linux kernel stable tree

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

media: v4l2-ctrls: validate HEVC active reference counts - kernel/git/stable/linux.git - Linux kernel stable tree

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

media: v4l2-ctrls: validate HEVC active reference counts - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9a998cc1c348769262d433acb7d238c5fac4b2e0
generic

media: v4l2-ctrls: validate HEVC active reference counts - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3068ab802fc98b121dcb451e1f7f4d338ffc7a19

Vendor Advisories for CVE-2026-68206(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 / 49× 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:21 UTCEG score recompute
  2. 2026-08-21 03:21 UTCVendor advisory
  3. 2026-08-21 03:21 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 16:03 UTCGHSA enrichment
  6. 2026-08-20 04:43 UTCGHSA enrichment
  7. 2026-08-19 17:25 UTCEG score recompute
  8. 2026-08-19 17:25 UTCGHSA enrichment
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-19 16:55 UTCEG score recompute
  11. 2026-08-19 16:55 UTCGHSA enrichment
  12. 2026-08-19 14:16 UTCGHSA enrichment
  13. 2026-08-19 02:58 UTCGHSA enrichment
  14. 2026-08-18 15:38 UTCEG score recompute
  15. 2026-08-18 15:38 UTCGHSA enrichment
  16. 2026-08-18 13:49 UTCEPSS rescore
  17. 2026-08-18 13:49 UTCEPSS rescore
  18. 2026-08-18 04:17 UTCGHSA enrichment
  19. 2026-08-17 16:56 UTCEG score recompute
  20. 2026-08-17 16:56 UTCGHSA enrichment
  21. 2026-08-17 13:47 UTCEPSS rescore
  22. 2026-08-17 05:38 UTCEG score recompute
  23. 2026-08-17 05:38 UTCGHSA enrichment
  24. 2026-08-17 05:09 UTCEG score recompute
  25. 2026-08-17 05:09 UTCGHSA enrichment
Show 24 more
  1. 2026-08-16 19:14 UTCEG score recompute
  2. 2026-08-16 19:14 UTCGHSA enrichment
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 07:56 UTCEG score recompute
  5. 2026-08-16 07:56 UTCGHSA enrichment
  6. 2026-08-15 20:39 UTCGHSA enrichment
  7. 2026-08-15 09:22 UTCEG score recompute
  8. 2026-08-15 09:22 UTCGHSA enrichment
  9. 2026-08-15 01:30 UTCEPSS rescore
  10. 2026-08-14 22:05 UTCGHSA enrichment
  11. 2026-08-14 10:46 UTCEG score recompute
  12. 2026-08-14 10:46 UTCGHSA enrichment
  13. 2026-08-13 23:29 UTCEG score recompute
  14. 2026-08-13 23:29 UTCGHSA enrichment
  15. 2026-08-13 22:45 UTCEG score recompute▲ 7.80
  16. 2026-08-13 22:45 UTCGHSA enrichment
  17. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-13 14:41 UTCEG score recompute
  20. 2026-08-13 14:41 UTCGHSA enrichment
  21. 2026-08-12 13:51 UTCEPSS rescore
  22. 2026-08-10 13:24 UTCNVD update
  23. 2026-08-10 12:20 UTCEG score recompute
  24. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68206?
CVE-2026-68206 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: media: v4l2-ctrls: validate HEVC active reference counts HEVC slice parameters are shared stateless V4L2 controls, but the common validation path does not verify the active L0/L1 reference counts before driver-specific code…
When was CVE-2026-68206 disclosed?
CVE-2026-68206 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-68206 actively exploited?
CVE-2026-68206 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.6% of all scored CVEs.
What is the CVSS score of CVE-2026-68206?
CVE-2026-68206 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-68206?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68206, 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-68206

Explore →

Is Your Infrastructure Affected by CVE-2026-68206?

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

Start Free Scan →Browse All CVEs