Answer in brief
CVE-2026-64524 records a Unknown severity vulnerability in drm/hyperv: validate resolution_count and fix WIN8 fallback. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-64524 records a Unknown severity vulnerability in drm/hyperv: validate resolution_count and fix WIN8 fallback. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=76c56a5affeba1e163b66b9d8cc192e6154466f0 <96f7de3172d4aa878b7f87173b2b3507c350fcd6 || >=76c56a5affeba1e163b66b9d8cc192e6154466f0 <bc573752f3dac0d1ab8df7078c1851bc76717653 || >=76c56a5affeba1e163b66b9d8cc192e6154466f0 <1fb565b77b8f44afabb02de6310065f109d89e94 || >=76c56a5affeba1e163b66b9d8cc192e6154466f0 <a321c908f2eeea01539668eb270d074d9b88e490 || >=76c56a5affeba1e163b66b9d8cc192e6154466f0 <9c698b2c43c2667c34f5336bf46ad5786216ac2a || >=76c56a5affeba1e163b66b9d8cc192e6154466f0 <8a114b25b5521eae451b13bce98ae978624962e5 || >=76c56a5affeba1e163b66b9d8cc192e6154466f0 <13d33b9ef67066c77c84273fac5a1d3fde3533d1 | 96f7de3172d4aa878b7f87173b2b3507c350fcd6, bc573752f3dac0d1ab8df7078c1851bc76717653, 1fb565b77b8f44afabb02de6310065f109d89e94, a321c908f2eeea01539668eb270d074d9b88e490, 9c698b2c43c2667c34f5336bf46ad5786216ac2a, 8a114b25b5521eae451b13bce98ae978624962e5, 13d33b9ef67066c77c84273fac5a1d3fde3533d1 |
| Linux/Linuxgeneric | 5.14 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=76c56a5affeba1e163b66b9d8cc192e6154466f0 <96f7de3172d4aa878b7f87173b2b3507c350fcd6 || >=76c56a5affeba1e163b66b9d8cc192e6154466f0 <bc573752f3dac0d1ab8df7078c1851bc76717653 || >=76c56a5affeba1e163b66b9d8cc192e6154466f0 <1fb565b77b8f44afabb02de6310065f109d89e94 || >=76c56a5affeba1e163b66b9d8cc192e6154466f0 <a321c908f2eeea01539668eb270d074d9b88e490 || >=76c56a5affeba1e163b66b9d8cc192e6154466f0 <9c698b2c43c2667c34f5336bf46ad5786216ac2a || >=76c56a5affeba1e163b66b9d8cc192e6154466f0 <8a114b25b5521eae451b13bce98ae978624962e5 || >=76c56a5affeba1e163b66b9d8cc192e6154466f0 <13d33b9ef67066c77c84273fac5a1d3fde3533d1 | 96f7de3172d4aa878b7f87173b2b3507c350fcd6, bc573752f3dac0d1ab8df7078c1851bc76717653, 1fb565b77b8f44afabb02de6310065f109d89e94, a321c908f2eeea01539668eb270d074d9b88e490, 9c698b2c43c2667c34f5336bf46ad5786216ac2a, 8a114b25b5521eae451b13bce98ae978624962e5, 13d33b9ef67066c77c84273fac5a1d3fde3533d1 |
| Linux/Linuxgeneric | 5.14 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.