# CVE-2026-64516: drm/amdgpu/vce1: Fix VCE 1 firmware size and offsets

> A missing offset calculation in the AMD GPU VCE1 driver allows out-of-bounds memory access, potentially leading to code execution or system crashes.

- **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:** 25 Jul 2026
- **Updated:** 5 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-64516, GHSA-q3hq-vwmg-m826, ROOT-OS-UBUNTU-2204-CVE-2026-64516, UBUNTU-CVE-2026-64516

## What is CVE-2026-64516?

CVE-2026-64516 is a high-severity memory corruption vulnerability in Linux, published on 25 Jul 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/vce1: Fix VCE 1 firmware size and offsets

The VCPU BO contains the actual FW at an offset, but
it was not calculated into the VCPU BO size.
Subtract this from the FW size to make sure there is
no out of bounds access.

Make sure the stack and data offsets are aligned to
the 32K TLB size.

Check that the FW microcode actually fits in the
space that is reserved for it.

(cherry picked from commit c16fe59f622a080fc457a57b3e8f14c780699449)

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


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

Apply the vendor's patch.

## Is CVE-2026-64516 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-64516 is a high-severity memory corruption vulnerability in Linux, published on 25 Jul 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-64516 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-64516/ (Markdown: https://insights.sbomify.com/CVE-2026-64516/index.md)
```

## Sources

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

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