Answer in brief
CVE-2026-68254 records a Unknown severity vulnerability in drm/i915/vrr: require valid min/max vfreq for VRR. 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 | >=117cd09ba52857a60dc5d7f61941046625d8ff5a <6598ac1721c3a5543efdbcab579a8561268d7ce1 || >=117cd09ba52857a60dc5d7f61941046625d8ff5a <f16218689b41efcbc491207cd7716477b1223879 || >=117cd09ba52857a60dc5d7f61941046625d8ff5a <df1582c0a101e2e2f133dd331d2a3258bb6a7518 || >=117cd09ba52857a60dc5d7f61941046625d8ff5a <c726c8bbee5115dad37fa7867136ebaa50690331 || >=117cd09ba52857a60dc5d7f61941046625d8ff5a <f8a9262c7a6fc2de9802e14b0228114f0333869e | 6598ac1721c3a5543efdbcab579a8561268d7ce1, f16218689b41efcbc491207cd7716477b1223879, df1582c0a101e2e2f133dd331d2a3258bb6a7518, c726c8bbee5115dad37fa7867136ebaa50690331, f8a9262c7a6fc2de9802e14b0228114f0333869e |
| Linux/Linuxgeneric | 5.12 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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)
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68254 records a Unknown severity vulnerability in drm/i915/vrr: require valid min/max vfreq for VRR. 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 | >=117cd09ba52857a60dc5d7f61941046625d8ff5a <6598ac1721c3a5543efdbcab579a8561268d7ce1 || >=117cd09ba52857a60dc5d7f61941046625d8ff5a <f16218689b41efcbc491207cd7716477b1223879 || >=117cd09ba52857a60dc5d7f61941046625d8ff5a <df1582c0a101e2e2f133dd331d2a3258bb6a7518 || >=117cd09ba52857a60dc5d7f61941046625d8ff5a <c726c8bbee5115dad37fa7867136ebaa50690331 || >=117cd09ba52857a60dc5d7f61941046625d8ff5a <f8a9262c7a6fc2de9802e14b0228114f0333869e | 6598ac1721c3a5543efdbcab579a8561268d7ce1, f16218689b41efcbc491207cd7716477b1223879, df1582c0a101e2e2f133dd331d2a3258bb6a7518, c726c8bbee5115dad37fa7867136ebaa50690331, f8a9262c7a6fc2de9802e14b0228114f0333869e |
| Linux/Linuxgeneric | 5.12 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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)
Quoted source text, attributed separately from HOL analysis.