CVE-2026-68108

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.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: 8.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:

drm/amdgpu/vce: fix integer overflow in image size

Fix a security vulnerability where malicious VCE command streams with oversized dimensions (e.g. 65536×65536) cause 32-bit integer overflow, wrapping the calculated buffer size to 0. This bypasses validation and allows GPU firmware to perform out-of-bound memory access.

The fix uses 64-bit arithmetic to detect overflow and rejects invalid dimensions before they reach the hardware.

V2: remove redundant check V3: modify max height value V4: remove size64

(cherry picked from commit cbe408dba581755ad1279a487ec786d8927d778d)

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
44(Track)
EG Risk 44/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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
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

drm/amdgpu/vce: fix integer overflow in image size - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu/vce: fix integer overflow in image size - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu/vce: fix integer overflow in image size - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/amdgpu/vce: fix integer overflow in image size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/186bfdc4e26d019b2e7570cb121964a1d89b2e5b
generic

drm/amdgpu/vce: fix integer overflow in image size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/00c311a13d225266800c712f2b7db2711c6897de

Vendor Advisories for CVE-2026-68108(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 32× in last 7d / 47× 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 18:23 UTCGHSA enrichment
  3. 2026-08-20 05:55 UTCGHSA enrichment
  4. 2026-08-19 17:26 UTCEG score recompute
  5. 2026-08-19 17:26 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 16:56 UTCEG score recompute
  8. 2026-08-19 16:56 UTCGHSA enrichment
  9. 2026-08-19 08:50 UTCGHSA enrichment
  10. 2026-08-18 20:20 UTCEG score recompute
  11. 2026-08-18 20:20 UTCGHSA enrichment
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-18 07:51 UTCGHSA enrichment
  14. 2026-08-17 19:22 UTCEG score recompute
  15. 2026-08-17 19:22 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 05:41 UTCEG score recompute
  18. 2026-08-17 05:41 UTCGHSA enrichment
  19. 2026-08-17 05:12 UTCEG score recompute
  20. 2026-08-17 05:12 UTCGHSA enrichment
  21. 2026-08-17 02:22 UTCEG score recompute
  22. 2026-08-17 02:22 UTCGHSA enrichment
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 13:53 UTCEG score recompute
  25. 2026-08-16 13:53 UTCGHSA enrichment
Show 22 more
  1. 2026-08-16 01:25 UTCGHSA enrichment
  2. 2026-08-15 12:57 UTCEG score recompute
  3. 2026-08-15 12:57 UTCGHSA enrichment
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-15 00:28 UTCGHSA enrichment
  6. 2026-08-14 11:59 UTCEG score recompute
  7. 2026-08-14 11:59 UTCGHSA enrichment
  8. 2026-08-13 23:31 UTCEG score recompute
  9. 2026-08-13 23:31 UTCGHSA enrichment
  10. 2026-08-13 22:46 UTCEG score recompute▲ 8.80
  11. 2026-08-13 22:46 UTCGHSA enrichment
  12. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-13 00:22 UTCGHSA enrichment
  15. 2026-08-13 00:22 UTCNVD update
  16. 2026-08-13 00:06 UTCEG score recompute
  17. 2026-08-13 00:06 UTCGHSA enrichment
  18. 2026-08-13 00:05 UTCMITRE cvelistV5
  19. 2026-08-12 13:51 UTCEPSS rescore
  20. 2026-08-10 13:24 UTCNVD update
  21. 2026-08-10 12:22 UTCEG score recompute
  22. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68108?
CVE-2026-68108 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vce: fix integer overflow in image size Fix a security vulnerability where malicious VCE command streams with oversized dimensions (e.g. 65536×65536) cause 32-bit integer overflow, wrapping the calculated buffer size to…
When was CVE-2026-68108 disclosed?
CVE-2026-68108 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-68108 actively exploited?
CVE-2026-68108 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 96.5% of all scored CVEs.
What is the CVSS score of CVE-2026-68108?
CVE-2026-68108 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-68108?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68108, 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-68108

Explore →

Is Your Infrastructure Affected by CVE-2026-68108?

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

Start Free Scan →Browse All CVEs