CVE-2026-68254: Linux kernel · drm/i915/vrr: require valid min/max vfreq for VRR
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f16218689b41efcbc491207cd7716477b1223879 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 17:04 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in f16218689b41efcbc491207cd7716477b1223879, f8a9262c7a6fc2de9802e14b0228114f0333869e, df1582c0a101e2e2f133dd331d2a3258bb6a7518 +4
Exploitation evidence
Disclosed: evidence found.
CVE published 10 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
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)
References
- git.kernel.org/stable/c/2f9aa8d42b7fc17621894456433ac07689fb4a21 (opens in a new tab)
- git.kernel.org/stable/c/5225122b9cad6b0c61e767fb2adea8c07da925be (opens in a new tab)
- git.kernel.org/stable/c/6598ac1721c3a5543efdbcab579a8561268d7ce1 (opens in a new tab)
- git.kernel.org/stable/c/f16218689b41efcbc491207cd7716477b1223879 (opens in a new tab)
- git.kernel.org/stable/c/df1582c0a101e2e2f133dd331d2a3258bb6a7518 (opens in a new tab)
- git.kernel.org/stable/c/c726c8bbee5115dad37fa7867136ebaa50690331 (opens in a new tab)
- git.kernel.org/stable/c/f8a9262c7a6fc2de9802e14b0228114f0333869e (opens in a new tab)