CVE Catalog

CVE-2026-64524

HighCVSS 7.7
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.14%

4th percentile - higher than 4% of all known CVEs

Summary

In the Linux kernel DRM Hyper-V driver, the resolution_count field in SYNTHVID_RESOLUTION_RESPONSE was not validated, potentially causing an out-of-bounds read of the supported_resolution array. Also, when the WIN10 resolution probe failed, screen_*_max / preferred_* were left unset, causing all userspace framebuffers to be rejected.

Risk Assessment

The organization may experience display system failures in Hyper-V environments, preventing graphical applications and remote desktop from functioning.

Recommendation

Apply the Linux kernel patch that validates resolution_count and sets default WIN8 values when the WIN10 probe fails.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS