drm/i915/vrr: require valid min/max vfreq for VRR
3Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackepss 0.2%
exploitation probability
0.2%top 93% of all CVEs
observed exploitation
nono source reports it
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)
Affected products
Linux · LinuxReferences
https://git.kernel.org/stable/c/2f9aa8d42b7fc17621894456433ac07689fb4a21https://git.kernel.org/stable/c/5225122b9cad6b0c61e767fb2adea8c07da925behttps://git.kernel.org/stable/c/6598ac1721c3a5543efdbcab579a8561268d7ce1https://git.kernel.org/stable/c/c726c8bbee5115dad37fa7867136ebaa50690331https://git.kernel.org/stable/c/df1582c0a101e2e2f133dd331d2a3258bb6a7518https://git.kernel.org/stable/c/f16218689b41efcbc491207cd7716477b1223879https://git.kernel.org/stable/c/f8a9262c7a6fc2de9802e14b0228114f0333869e