drm/amdgpu/vce1: Fix VCE 1 firmware size and offsets
Summary
| CVE | CVE-2026-64516 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-07-25 10:17:37 UTC |
| Updated | 2026-07-25 10:17:37 UTC |
| 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) |
Risk And Classification
EPSS: 0.001980000 probability, percentile 0.097860000 (date 2026-07-25)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected d4a640d4b9f34aa9472c71986ef4b5a42dbe4f0f ce0de178ef08408f6ba8f2e9a13bf52fbe5852f4 git | Not specified |
| CNA | Linux | Linux | affected d4a640d4b9f34aa9472c71986ef4b5a42dbe4f0f 3e5a1d5bb2ff061e64c7992f8e5404dfd4c2d0f3 git | Not specified |
| CNA | Linux | Linux | affected 6.19 | Not specified |
| CNA | Linux | Linux | unaffected 6.19 semver | Not specified |
| CNA | Linux | Linux | unaffected 7.0.11 7.0.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/3e5a1d5bb2ff061e64c7992f8e5404dfd4c2d0f3 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/ce0de178ef08408f6ba8f2e9a13bf52fbe5852f4 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.