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… (CVE-2026-64516)
A vulnerability in the Linux kernel's AMDGPU driver (specifically drm/amdgpu/vce1) involved incorrect calculation of the VCPU buffer object size related to firmware offsets. This could lead to out-of-bounds access due to misaligned stack and data offsets and insufficient space reserved for firmware microcode. The issue has been resolved by correcting the size calculation and alignment checks.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's AMDGPU driver (drm/amdgpu/vce1) was caused by not including the offset of the actual firmware within the VCPU buffer object size calculation. This omission risked out-of-bounds memory access. The fix ensures the firmware size accounts for this offset, aligns stack and data offsets to the 32K TLB size, and verifies that the firmware microcode fits within the reserved space. The patch was applied via commit c16fe59f622a080fc457a57b3e8f14c780699449.
Potential Impact
The vulnerability could potentially allow out-of-bounds memory access within the AMDGPU driver's firmware handling, which might lead to memory corruption or stability issues. However, no known exploits are reported in the wild. The exact impact on confidentiality, integrity, or availability is not detailed in the provided information.
Mitigation Recommendations
A fix has been applied in the Linux kernel to address this vulnerability by correcting the firmware size calculation and alignment. Users should update to a Linux kernel version that includes the patch from commit c16fe59f622a080fc457a57b3e8f14c780699449. Patch status is confirmed by the vendor commit. There is no indication that additional mitigation steps are required.
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… (CVE-2026-64516)
Description
A vulnerability in the Linux kernel's AMDGPU driver (specifically drm/amdgpu/vce1) involved incorrect calculation of the VCPU buffer object size related to firmware offsets. This could lead to out-of-bounds access due to misaligned stack and data offsets and insufficient space reserved for firmware microcode. The issue has been resolved by correcting the size calculation and alignment checks.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's AMDGPU driver (drm/amdgpu/vce1) was caused by not including the offset of the actual firmware within the VCPU buffer object size calculation. This omission risked out-of-bounds memory access. The fix ensures the firmware size accounts for this offset, aligns stack and data offsets to the 32K TLB size, and verifies that the firmware microcode fits within the reserved space. The patch was applied via commit c16fe59f622a080fc457a57b3e8f14c780699449.
Potential Impact
The vulnerability could potentially allow out-of-bounds memory access within the AMDGPU driver's firmware handling, which might lead to memory corruption or stability issues. However, no known exploits are reported in the wild. The exact impact on confidentiality, integrity, or availability is not detailed in the provided information.
Mitigation Recommendations
A fix has been applied in the Linux kernel to address this vulnerability by correcting the firmware size calculation and alignment. Users should update to a Linux kernel version that includes the patch from commit c16fe59f622a080fc457a57b3e8f14c780699449. Patch status is confirmed by the vendor commit. There is no indication that additional mitigation steps are required.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-q3hq-vwmg-m826
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64516"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a6542059c2644c7f8081885
Added to database: 07/25/2026, 23:08:53 UTC
Last enriched: 07/25/2026, 23:10:44 UTC
Last updated: 07/26/2026, 06:11:58 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.