# CVE-2026-68254: drm/i915/vrr: require valid min/max vfreq for VRR

> A missing validation in the Intel i915 GPU driver allows a local attacker to trigger a division by zero, causing a system crash.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 23 Aug 2026
- **Also known as:** AZL-94932, BELL-CVE-2026-68254, DEBIAN-CVE-2026-68254, GHSA-pg4j-qqhw-89pg, UBUNTU-CVE-2026-68254

## What is CVE-2026-68254?

CVE-2026-68254 is a denial of service vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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)

## Which versions are affected by CVE-2026-68254?


## How do I fix CVE-2026-68254?

Apply the vendor's patch.

## Is CVE-2026-68254 being exploited?

There is no known exploitation of CVE-2026-68254 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68254 and fix it if it is affected.

What it is: CVE-2026-68254 is a denial of service vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-68254 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68254/ (Markdown: https://insights.sbomify.com/CVE-2026-68254/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68254
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68254
- OSV: https://osv.dev/vulnerability/CVE-2026-68254

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68254/
Summaries are generated and may contain mistakes; the official description above is the record.