CVE-2026-68254
drm/i915/vrr: require valid min/max vfreq for VRR
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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)
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
5.12
References 7
git.kernel.org
- stable/c/2f9aa8d42b7fc17621894456433ac07689fb4a21
- stable/c/5225122b9cad6b0c61e767fb2adea8c07da925be
- stable/c/6598ac1721c3a5543efdbcab579a8561268d7ce1
- stable/c/f16218689b41efcbc491207cd7716477b1223879
- stable/c/df1582c0a101e2e2f133dd331d2a3258bb6a7518
- stable/c/c726c8bbee5115dad37fa7867136ebaa50690331
- stable/c/f8a9262c7a6fc2de9802e14b0228114f0333869e