CVE-2026-64524
drm/hyperv: validate resolution_count and fix WIN8 fallback
Description
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.
INFO
Published Date :
July 25, 2026, 10:17 a.m.
Last Modified :
July 25, 2026, 10:17 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-64524
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Update the Linux kernel to the latest version.
- Apply patches addressing resolution count validation.
- Ensure fallback logic handles resolution probe failures correctly.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-64524.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-64524 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-64524
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-64524 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-64524 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 25, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '76c56a5affeba1e163b66b9d8cc192e6154466f0', 'lessThan': '96f7de3172d4aa878b7f87173b2b3507c350fcd6', 'versionType': 'git'}, {'status': 'affected', 'version': '76c56a5affeba1e163b66b9d8cc192e6154466f0', 'lessThan': 'bc573752f3dac0d1ab8df7078c1851bc76717653', 'versionType': 'git'}, {'status': 'affected', 'version': '76c56a5affeba1e163b66b9d8cc192e6154466f0', 'lessThan': '1fb565b77b8f44afabb02de6310065f109d89e94', 'versionType': 'git'}, {'status': 'affected', 'version': '76c56a5affeba1e163b66b9d8cc192e6154466f0', 'lessThan': 'a321c908f2eeea01539668eb270d074d9b88e490', 'versionType': 'git'}, {'status': 'affected', 'version': '76c56a5affeba1e163b66b9d8cc192e6154466f0', 'lessThan': '9c698b2c43c2667c34f5336bf46ad5786216ac2a', 'versionType': 'git'}, {'status': 'affected', 'version': '76c56a5affeba1e163b66b9d8cc192e6154466f0', 'lessThan': '8a114b25b5521eae451b13bce98ae978624962e5', 'versionType': 'git'}, {'status': 'affected', 'version': '76c56a5affeba1e163b66b9d8cc192e6154466f0', 'lessThan': '13d33b9ef67066c77c84273fac5a1d3fde3533d1', 'versionType': 'git'}], 'programFiles': ['drivers/gpu/drm/hyperv/hyperv_drm_proto.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '5.14'}, {'status': 'unaffected', 'version': '0', 'lessThan': '5.14', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.15.210', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.176', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.143', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.93', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.35', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.12', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/gpu/drm/hyperv/hyperv_drm_proto.c'], 'defaultStatus': 'affected'}] Added Description 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. Added Reference https://git.kernel.org/stable/c/13d33b9ef67066c77c84273fac5a1d3fde3533d1 Added Reference https://git.kernel.org/stable/c/1fb565b77b8f44afabb02de6310065f109d89e94 Added Reference https://git.kernel.org/stable/c/8a114b25b5521eae451b13bce98ae978624962e5 Added Reference https://git.kernel.org/stable/c/96f7de3172d4aa878b7f87173b2b3507c350fcd6 Added Reference https://git.kernel.org/stable/c/9c698b2c43c2667c34f5336bf46ad5786216ac2a Added Reference https://git.kernel.org/stable/c/a321c908f2eeea01539668eb270d074d9b88e490 Added Reference https://git.kernel.org/stable/c/bc573752f3dac0d1ab8df7078c1851bc76717653