# CVE-2026-68108: drm/amdgpu/vce: fix integer overflow in image size

> A malicious VCE command stream can trigger an integer overflow in the AMD GPU driver, leading to out-of-bounds memory access and potential code execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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-68108, DEBIAN-CVE-2026-68108, GHSA-34qj-qvm5-mprq, UBUNTU-CVE-2026-68108

## What is CVE-2026-68108?

CVE-2026-68108 is a high-severity 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/vce: fix integer overflow in image size

Fix a security vulnerability where malicious VCE command streams
with oversized dimensions (e.g. 65536×65536) cause 32-bit integer
overflow, wrapping the calculated buffer size to 0. This bypasses
validation and allows GPU firmware to perform out-of-bound memory
access.

The fix uses 64-bit arithmetic to detect overflow and rejects
invalid dimensions before they reach the hardware.

V2: remove redundant check
V3: modify max height value
V4: remove size64

(cherry picked from commit cbe408dba581755ad1279a487ec786d8927d778d)

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

Apply the vendor's patch.

## Is CVE-2026-68108 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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