The Hyper‑V DRM driver in the Linux kernel has an unchecked bounds condition when parsing a SYNTHVID_RESOLUTION_RESPONSE message. If the resolution_count reported by a guest exceeds 64, the driver walks past the end of the supported_resolution array, resulting in a buffer over‑read. In addition, when the Win10 resolution probe fails, the driver leaves screen dimension fields uninitialized causing drm_internal_framebuffer_create() to reject all userspace framebuffers with an error. The net effect is that graphical applications cannot create framebuffers, effectively denying graphical services to users of the affected driver. The CVE description does not indicate kernel memory corruption or privilege escalation, only a denial‑of‑service scenario.

All Linux kernel releases that contain the Hyper‑V DRM driver prior to the inclusion of the commit identified by 13d33b9ef67066c77c84273fac5a1d3fde3533d1 are affected. This encompasses any kernel version that has not incorporated this patch, regardless of vendor distribution, as the vulnerability is inherent to the generic Linux kernel Hyper‑V DRM component.

The CVSS score of 7.7 marks the flaw as high severity, yet the EPSS score of less than 1 % indicates that exploitation is currently considered unlikely. The vulnerability is not listed in CISA’s KEV catalog. Attackers would need local or guest‑OS access to the Hyper‑V DRM interface, such as interaction with /dev/dri/card*, to craft a SYNTHVID_RESOLUTION_RESPONSE with a large resolution_count or trigger a Windows probe failure. No privilege escalation beyond the local scope is suggested by the current description.