# CVE-2026-68106: drm/amdgpu: fix division by zero with invalid uvd dimensions

> A division by zero in the AMD GPU driver allows attackers to cause a system crash by providing invalid video dimensions.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-68106, DEBIAN-CVE-2026-68106, GHSA-jxfv-759v-w83r, UBUNTU-CVE-2026-68106

## What is CVE-2026-68106?

CVE-2026-68106 is a high-severity 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/amdgpu: fix division by zero with invalid uvd dimensions

When width or height is less than 16, width_in_mb or height_in_mb
becomes 0, leading to fs_in_mb being 0. This causes a division by
zero when calculating num_dpb_buffer in H264 and H264 Perf decode
paths.

Add validation to reject frames with width < 16 or height < 16
before performing any calculations that depend on these values.

V2: Format change - move up all vaiable definitions.
V3: Use warn_once to avoid spam.

(cherry picked from commit 3e41d26c70b0a459d041cc19482a226c4b7423cb)

Weakness: CWE-369 (Divide By Zero)

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


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

Apply the vendor's patch.

## Is CVE-2026-68106 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68106 is a high-severity 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-68106 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-68106/ (Markdown: https://insights.sbomify.com/CVE-2026-68106/index.md)
```

## Sources

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

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