Skip to content
Systems

CVE-2026-64516

8.8
High
EPSS 0.11%Patch availableJul 27, 2026

Linux kernel amdgpu VCE1 firmware size bug allows OOB access and potential kernel compromise

common questions

Is CVE-2026-64516 being exploited?

Not confirmed. CVE-2026-64516 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.11% probability of exploitation in the next 30 days.

How severe is CVE-2026-64516?

CVE-2026-64516 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-64516?

Yes. A fix has been recorded for CVE-2026-64516. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-64516 affect?

CVE-2026-64516 affects Linux kernel (amdgpu DRM), Systems with AMD GPUs using VCE1 firmware, Linux distributions using affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-64516?

Apply vendor kernel updates for affected systems and reboot hosts with AMD GPUs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (amdgpu DRM)Systems with AMD GPUs using VCE1 firmwareLinux distributions using affected kernels
impact

Out-of-bounds access in amdgpu VCE1 can corrupt kernel memory, enabling local privilege escalation or arbitrary code execution.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= d4a640d4b9f34aa9472c71986ef4b5a42dbe4f0f and < ce0de178ef08408f6ba8f2e9a13bf52fbe5852f4
  • affected>= d4a640d4b9f34aa9472c71986ef4b5a42dbe4f0f and < 3e5a1d5bb2ff061e64c7992f8e5404dfd4c2d0f3
  • affected6.19
vendor says fixed in< 6.19, >= 7.0.11 and <= 7.0.*, >= 7.1 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free