drm/i915/vrr: require valid min/max vfreq for VRR
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 117cd09ba52857a60dc5d7f61941046625d8ff5a · < c726c8bbee5115dad37fa7867136ebaa50690331| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/i915/vrr: require valid min/max vfreq for VRR
Ensure the EDID provided min/max vfreq are valid. Most scenarios are already covered (by coincidence) through the checks in intel_vrr_is_capable() and intel_vrr_is_in_range(), but be more explicit about it. At worst, a zero min_vfreq could lead to a division by zero in intel_vrr_compute_vmax().
Discovered using AI-assisted static analysis confirmed by Intel Product Security.
(cherry picked from commit 1765cf59f517b02f3b0591fe5120930d08bddeb6)
From the CVE record · Linux
The Linux kernel's i915 variable refresh rate code does not explicitly validate the minimum and maximum refresh frequencies provided by an EDID. A zero minimum frequency could cause a division by zero; the input does not establish whether an attacker can supply the EDID or what access or interaction that would require.
Engineers running Linux kernels with the i915 graphics driver should check their versions against the vendor advisory; affected versions were not provided.