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)
Published: 2026-08-10
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The Linux kernel’s graphics driver contains a flaw that does not explicitly validate the minimum and maximum vertical frequency values supplied via EDID for variable refresh rate (VRR). If an attacker supplies a zero min_vfreq, a division operation in intel_vrr_compute_vmax() will trigger a divide‑by‑zero error, potentially causing the kernel to panic. This flaw manifests as a denial of service that results in a system crash and loss of availability. The weakness corresponds to a divide‑by‑zero bug, captured by CWE‑254.

Affected Systems

The issue exists in the Linux kernel, affecting all versions prior to the inclusion of the fix referenced by commit 1765cf59f517b02f3b0591fe5120930d08bddeb6. Vendors distributing kernels that include this bug, including the mainline Linux distribution kernels, are affected. No specific product or patchlevel is enumerated in the CVE data beyond the generic Linux kernel.

Risk and Exploitability

While the CVSS score is not listed, the division‑by‑zero bug can lead to a kernel panic, indicating a high severity impact. The EPSS score is not available, and the vulnerability is not included in the CISA KEV catalog. The likely attack vector is local or privileged, inferred from the need to provide malformed EDID data to the graphics driver; however, the CVE description does not explicitly state how an attacker could supply such data. Given the potential to crash the system, this vulnerability is considered high risk for affected installations.

Generated by OpenCVE AI on August 10, 2026 at 14:42 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the kernel patch that includes commit 1765cf59f517b02f3b0591fe5120930d08bddeb6
  • Upgrade the Linux kernel to the latest stable release that includes the fix
  • If unable to upgrade immediately, validate that EDID min_vfreq is non‑zero before it is used by the driver (temporary mitigation)

Generated by OpenCVE AI on August 10, 2026 at 14:42 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 10 Aug 2026 15:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-254

Mon, 10 Aug 2026 12:30:00 +0000

Type Values Removed Values Added
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)
Title drm/i915/vrr: require valid min/max vfreq for VRR
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-10T12:01:20.400Z

Reserved: 2026-07-30T09:28:09.377Z

Link: CVE-2026-68254

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-10T19:45:04Z

Weaknesses