CVE-2026-64524

HIGHPre-NVD 7.77.7—
EchelonGraph scoreMEDIUM confidence

Score 7.7 from GitHub Security Advisory (severity: HIGH) published 2026-07-25. the CNA's CVSS baseline 7.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
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

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

drm/hyperv: validate resolution_count and fix WIN8 fallback

A SYNTHVID_RESOLUTION_RESPONSE with resolution_count > 64 walks past the supported_resolution[SYNTHVID_MAX_RESOLUTION_COUNT] array in the parse loop. Bound resolution_count against the array size, folded into the existing zero-check.

When the WIN10 resolution probe fails, the caller in hyperv_connect_vsp() left hv->screen_*_max / preferred_* unpopulated, which sets mode_config.max_width / max_height to 0 and makes drm_internal_framebuffer_create() reject every userspace framebuffer with -EINVAL. The pre-WIN10 branch had the same gap for preferred_width / preferred_height. Use a single post-probe fallback guarded by screen_width_max == 0 so both paths converge on the WIN8 defaults.

CVSS v3
7.7
EG Score
7.7(medium)
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
4%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 5, 2026

Advisory Details (7)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

drm/hyperv: validate resolution_count and fix WIN8 fallback - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/hyperv: validate resolution_count and fix WIN8 fallback - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/hyperv: validate resolution_count and fix WIN8 fallback - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/hyperv: validate resolution_count and fix WIN8 fallback - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/96f7de3172d4aa878b7f87173b2b3507c350fcd6
generic

drm/hyperv: validate resolution_count and fix WIN8 fallback - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/hyperv: validate resolution_count and fix WIN8 fallback - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1fb565b77b8f44afabb02de6310065f109d89e94
generic

drm/hyperv: validate resolution_count and fix WIN8 fallback - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/13d33b9ef67066c77c84273fac5a1d3fde3533d1

Vendor Advisories for CVE-2026-64524(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-15ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-15ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-15ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-15ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)7.0.12-1—

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 26× in last 7d / 123× 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.

Showing the most recent 100 of 248 total refreshes for this CVE.

  1. 2026-09-15 09:18 UTCEG score recompute
  2. 2026-09-15 09:18 UTCVendor advisory
  3. 2026-09-15 09:18 UTCGHSA enrichment
  4. 2026-09-14 07:00 UTCVendor advisory
  5. 2026-09-14 07:00 UTCGHSA enrichment
  6. 2026-09-13 18:35 UTCEG score recompute
  7. 2026-09-13 18:35 UTCVendor advisory
  8. 2026-09-13 18:35 UTCGHSA enrichment
  9. 2026-09-13 06:10 UTCVendor advisory
  10. 2026-09-13 06:10 UTCGHSA enrichment
  11. 2026-09-12 17:39 UTCEG score recompute
  12. 2026-09-12 17:39 UTCVendor advisory
  13. 2026-09-12 17:39 UTCGHSA enrichment
  14. 2026-09-12 04:55 UTCVendor advisory
  15. 2026-09-12 04:55 UTCGHSA enrichment
  16. 2026-09-11 16:20 UTCEG score recompute
  17. 2026-09-11 16:20 UTCVendor advisory
  18. 2026-09-11 16:20 UTCGHSA enrichment
  19. 2026-09-11 09:37 UTCEPSS rescore
  20. 2026-09-10 22:51 UTCVendor advisory
  21. 2026-09-10 22:51 UTCGHSA enrichment
  22. 2026-09-10 10:24 UTCEG score recompute
  23. 2026-09-10 10:24 UTCVendor advisory
  24. 2026-09-10 10:24 UTCGHSA enrichment
  25. 2026-09-09 08:29 UTCVendor advisory
Show 75 more
  1. 2026-09-09 08:28 UTCGHSA enrichment
  2. 2026-09-07 21:10 UTCEG score recompute
  3. 2026-09-07 21:10 UTCVendor advisory
  4. 2026-09-07 21:10 UTCGHSA enrichment
  5. 2026-09-07 16:01 UTCEPSS rescore
  6. 2026-09-06 23:59 UTCEG score recompute
  7. 2026-09-06 23:59 UTCVendor advisory
  8. 2026-09-06 23:59 UTCGHSA enrichment
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-06 07:53 UTCVendor advisory
  11. 2026-09-06 07:53 UTCGHSA enrichment
  12. 2026-09-05 19:18 UTCEG score recompute
  13. 2026-09-05 19:18 UTCVendor advisory
  14. 2026-09-05 19:17 UTCGHSA enrichment
  15. 2026-09-05 15:31 UTCEPSS rescore
  16. 2026-09-05 05:54 UTCEG score recompute
  17. 2026-09-05 05:54 UTCVendor advisory
  18. 2026-09-05 05:54 UTCGHSA enrichment
  19. 2026-09-04 12:37 UTCEG score recompute
  20. 2026-09-04 12:37 UTCGHSA enrichment
  21. 2026-09-04 05:07 UTCEPSS rescore
  22. 2026-09-02 14:12 UTCEPSS rescore
  23. 2026-09-01 23:06 UTCEG score recompute
  24. 2026-09-01 23:06 UTCVendor advisory
  25. 2026-09-01 23:06 UTCGHSA enrichment
  26. 2026-09-01 13:54 UTCEPSS rescore
  27. 2026-09-01 04:40 UTCEPSS rescore
  28. 2026-08-31 00:54 UTCEG score recompute
  29. 2026-08-31 00:54 UTCVendor advisory
  30. 2026-08-31 00:54 UTCGHSA enrichment
  31. 2026-08-30 19:17 UTCEPSS rescore
  32. 2026-08-30 12:29 UTCEG score recompute
  33. 2026-08-30 12:29 UTCVendor advisory
  34. 2026-08-30 12:29 UTCGHSA enrichment
  35. 2026-08-30 01:22 UTCEPSS rescore
  36. 2026-08-30 00:00 UTCEG score recompute
  37. 2026-08-30 00:00 UTCVendor advisory
  38. 2026-08-30 00:00 UTCGHSA enrichment
  39. 2026-08-28 21:42 UTCEPSS rescore
  40. 2026-08-27 22:18 UTCEG score recompute
  41. 2026-08-27 22:18 UTCVendor advisory
  42. 2026-08-27 22:18 UTCGHSA enrichment
  43. 2026-08-27 09:53 UTCVendor advisory
  44. 2026-08-27 09:53 UTCGHSA enrichment
  45. 2026-08-26 19:55 UTCEG score recompute
  46. 2026-08-26 19:55 UTCVendor advisory
  47. 2026-08-26 19:55 UTCGHSA enrichment
  48. 2026-08-26 14:47 UTCEPSS rescore
  49. 2026-08-26 07:31 UTCVendor advisory
  50. 2026-08-26 07:31 UTCGHSA enrichment
  51. 2026-08-25 19:06 UTCEG score recompute
  52. 2026-08-25 19:06 UTCVendor advisory
  53. 2026-08-25 19:06 UTCGHSA enrichment
  54. 2026-08-25 13:49 UTCEPSS rescore
  55. 2026-08-25 06:40 UTCVendor advisory
  56. 2026-08-25 06:40 UTCGHSA enrichment
  57. 2026-08-24 18:00 UTCEG score recompute
  58. 2026-08-24 18:00 UTCVendor advisory
  59. 2026-08-24 18:00 UTCGHSA enrichment
  60. 2026-08-24 05:25 UTCVendor advisory
  61. 2026-08-24 05:25 UTCGHSA enrichment
  62. 2026-08-23 17:00 UTCVendor advisory
  63. 2026-08-23 17:00 UTCGHSA enrichment
  64. 2026-08-23 04:36 UTCEG score recompute
  65. 2026-08-23 04:36 UTCVendor advisory
  66. 2026-08-23 04:36 UTCGHSA enrichment
  67. 2026-08-23 00:19 UTCEPSS rescore
  68. 2026-08-22 16:11 UTCVendor advisory
  69. 2026-08-22 16:10 UTCGHSA enrichment
  70. 2026-08-22 03:45 UTCEG score recompute
  71. 2026-08-22 03:45 UTCVendor advisory
  72. 2026-08-22 03:45 UTCGHSA enrichment
  73. 2026-08-21 23:49 UTCEPSS rescore
  74. 2026-08-21 15:20 UTCVendor advisory
  75. 2026-08-21 15:20 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-64524?
CVE-2026-64524 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/hyperv: validate resolution_count and fix WIN8 fallback A SYNTHVIDRESOLUTIONRESPONSE with resolution_count > 64 walks past the supportedresolution[SYNTHVIDMAXRESOLUTIONCOUNT] array in the parse loop. Bound resolution_count…
When was CVE-2026-64524 disclosed?
CVE-2026-64524 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64524 actively exploited?
CVE-2026-64524 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.2% of all scored CVEs.
What is the CVSS score of CVE-2026-64524?
CVE-2026-64524 has a CVSS v4.0 base score of 7.7 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-64524?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64524, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64524

Explore →

Is Your Infrastructure Affected by CVE-2026-64524?

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

Start Free Scan →Browse All CVEs