drm/i915/vrr: require valid min/max vfreq for VRR
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)
CVE-2026-68254
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: osv:CVE-2026-68254
Kernel
Source reference: /affected/1/package/name
- Affected versions
- Not stated in this record
- Fixed versions
- 5.15.217
Source reference:
/affected/1/ranges6.1.184Source reference:
/affected/1/ranges6.6.151Source reference:
/affected/1/ranges6.12.103Source reference:
/affected/1/ranges6.18.44Source reference:
/affected/1/ranges7.1.6Source reference:
/affected/1/ranges - Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "117cd09ba52857a60dc5d7f61941046625d8ff5a"
},
{
"fixed": "2f9aa8d42b7fc17621894456433ac07689fb4a21"
},
{
"fixed": "5225122b9cad6b0c61e767fb2adea8c07da925be"
},
{
"fixed": "6598ac1721c3a5543efdbcab579a8561268d7ce1"
},
{
"fixed": "f16218689b41efcbc491207cd7716477b1223879"
},
{
"fixed": "df1582c0a101e2e2f133dd331d2a3258bb6a7518"
},
{
"fixed": "c726c8bbee5115dad37fa7867136ebaa50690331"
},
{
"fixed": "f8a9262c7a6fc2de9802e14b0228114f0333869e"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-68254.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.12.0"
},
{
"fixed": "5.15.217"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.184"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.151"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.103"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.44"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.1.6"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-68254.json"
}
}
]- Related CVEs
- CVE-2026-68254
Source reference:
/id
Publisher severity
No explicit severity was provided.
- Event
- #50736 · Revision 1
- Added to Heist Feed
- Publisher date