CVE-2026-68255

HIGHPre-NVD 7.77.7—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.7EG
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.7Exploit: 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/virtio: bound EDID block reads to the response buffer

virtio_get_edid_block() validates the read offset only against the device-supplied resp->size field, never against the fixed-size resp->edid array. The EDID block index is driven by the device-supplied extension count, so a malicious virtio-gpu backend can advertise a large size together with a high block count and read far past the array into adjacent kernel memory, which is then surfaced in the parsed EDID (an out-of-bounds read / info leak).

Also reject any read whose end exceeds the size of the edid array. Conforming EDID responses stay within the array and are unaffected.

CVSS v3
7.7
EG Score
7.7(high)
EG Risk
39(Track)
EG Risk 39/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
Severity77% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
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/virtio: bound EDID block reads to the response buffer - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/virtio: bound EDID block reads to the response buffer - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/virtio: bound EDID block reads to the response buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/375c1934ef0196d3b6d3a1eae3232bef8dae7bf7
generic

drm/virtio: bound EDID block reads to the response buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/35be0e2c6862abcd5e5f5445261f1fd910d4a9b4
generic

drm/virtio: bound EDID block reads to the response buffer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2757e6e803092cf0aeaf4b735e16b5d3bdc705c5

Vendor Advisories for CVE-2026-68255(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 35× in last 7d / 41× 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 06:11 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:54 UTCEG score recompute
  6. 2026-08-19 16:54 UTCGHSA enrichment
  7. 2026-08-19 10:25 UTCGHSA enrichment
  8. 2026-08-18 21:40 UTCEG score recompute
  9. 2026-08-18 21:40 UTCGHSA enrichment
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 08:22 UTCGHSA enrichment
  13. 2026-08-17 19:20 UTCGHSA enrichment
  14. 2026-08-17 05:38 UTCEG score recompute
  15. 2026-08-17 05:38 UTCGHSA enrichment
  16. 2026-08-17 05:08 UTCEG score recompute
  17. 2026-08-17 05:08 UTCGHSA enrichment
  18. 2026-08-17 04:22 UTCGHSA enrichment
  19. 2026-08-16 15:36 UTCEG score recompute
  20. 2026-08-16 15:36 UTCGHSA enrichment
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 02:50 UTCEG score recompute
  23. 2026-08-16 02:50 UTCGHSA enrichment
  24. 2026-08-15 14:04 UTCEG score recompute
  25. 2026-08-15 14:04 UTCGHSA enrichment
Show 16 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-15 01:18 UTCGHSA enrichment
  3. 2026-08-14 12:32 UTCEG score recompute
  4. 2026-08-14 12:32 UTCGHSA enrichment
  5. 2026-08-13 23:46 UTCEG score recompute
  6. 2026-08-13 23:46 UTCGHSA enrichment
  7. 2026-08-13 22:44 UTCEG score recompute▲ 7.70
  8. 2026-08-13 22:44 UTCGHSA enrichment
  9. 2026-08-13 22:44 UTCMITRE cvelistV5CVSS v3 → 7.7 · severity → HIGH
  10. 2026-08-13 22:00 UTCEPSS rescore
  11. 2026-08-13 17:00 UTCEG score recompute
  12. 2026-08-13 17:00 UTCGHSA enrichment
  13. 2026-08-12 13:51 UTCEPSS rescore
  14. 2026-08-10 13:24 UTCNVD update
  15. 2026-08-10 12:19 UTCEG score recompute
  16. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68255?
CVE-2026-68255 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/virtio: bound EDID block reads to the response buffer virtiogetedid_block() validates the read offset only against the device-supplied resp->size field, never against the fixed-size resp->edid array. The EDID block index is…
When was CVE-2026-68255 disclosed?
CVE-2026-68255 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-68255 actively exploited?
CVE-2026-68255 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 90.9% of all scored CVEs.
What is the CVSS score of CVE-2026-68255?
CVE-2026-68255 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-68255?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68255, 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-68255

Explore →

Is Your Infrastructure Affected by CVE-2026-68255?

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

Start Free Scan →Browse All CVEs