drm/hyperv: validate resolution_count and fix WIN8 fallback
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 76c56a5affeba1e163b66b9d8cc192e6154466f0 · < 8a114b25b5521eae451b13bce98ae978624962e5| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s drm/hyperv driver does not bound the resolution count in a SYNTHVID_RESOLUTION_RESPONSE, so a count above 64 causes the parser to read past an array. The report does not specify who can supply the response or whether authentication or user interaction is required. It also identifies a failed resolution probe that can leave display limits unset and cause userspace framebuffer creation to fail.
Engineers running Linux kernels with the drm/hyperv driver should check their kernel version against the vendor advisory; affected versions are not specified.