CVE-2026-64516
CVE CVE-2026-64516EUVD EUVD-2026-48860Published 2026-07-25T09:14:43.000ZLast changed 2026-08-05T12:42:33.000ZCVSS 8.8
What the advisory describes
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)
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux d4a640d4b9f34aa9472c71986ef4b5a42dbe4f0f <3e5a1d5bb2ff061e64c7992f8e5404dfd4c2d0f3; patch: 0; 6.19; d4a640d4b9f34aa9472c71986ef4b5a42dbe4f0f <ce0de178ef08408f6ba8f2e9a13bf52fbe5852f4; patch: 7.1; patch: 7.0.11
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.