CVE-2026-64524
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine without logging in. High risk of data exposure, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- ReservedThe CVE id was reserved by its CNA
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.7 HIGH (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-122
- Record status
- Awaiting Analysis
Attack profile CVSS 3.1 · 7.7
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-64524.md and follow it. Check whether this project is affected by CVE-2026-64524. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- https://git.kernel.org/stable/c/13d33b9ef67066c77c84273fac5a1d3fde3533d1
- https://git.kernel.org/stable/c/1fb565b77b8f44afabb02de6310065f109d89e94
- https://git.kernel.org/stable/c/8a114b25b5521eae451b13bce98ae978624962e5
- https://git.kernel.org/stable/c/96f7de3172d4aa878b7f87173b2b3507c350fcd6
- https://git.kernel.org/stable/c/9c698b2c43c2667c34f5336bf46ad5786216ac2a
- https://git.kernel.org/stable/c/a321c908f2eeea01539668eb270d074d9b88e490
- https://git.kernel.org/stable/c/bc573752f3dac0d1ab8df7078c1851bc76717653