Linux kernel amdgpu: unvalidated UVD decode message fields overflow the DPB size calculation
Impact
The UVD decode path took frame dimensions and H.265 reference counts straight from the guest-supplied decode message and fed them into the minimum DPB size arithmetic without bounds checks, so an oversized value overflows that calculation and yields a buffer smaller than the decoder will actually use. The kernel CNA split this across two ids covering the same missing-validation flaw in the same code path - CVE-2026-80908 rejects dimensions above 4096, CVE-2026-80909 rejects invalid H.265 reference counts - and the fix and the operator action are identical for both. Reach is limited: it needs a process that already holds an AMD render node and it only matters on ASICs that carry the UVD decode block, which compute-only Instinct fleets generally are not running decode workloads on. The upstream commits describe the overflow and the added rejection; they do not claim a demonstrated escalation, so treat this as driver hardening on shared AMD nodes rather than a break-glass event.
Who can reach it
Local user on the node with access to an AMD DRM render node - any tenant whose container has /dev/dri passed through for AMD GPU work. Host authentication required; no network path.
What to do
Move to a stable kernel carrying both commits and reboot the affected nodes; the validation is in the driver, so a drain-and-reboot per node is the only route and there is no runtime toggle. Nodes that are not using the UVD decode engine can be scheduled into a normal maintenance window rather than an emergency one. No AMD advisory or fixed distro version appears in the record - only the kernel stable commits.
Also covers 1 CVE
The vendor assigned a separate id to each affected code path. They share this advisory, this score and this fix, so they are one entry here.
References
Related entries
- Linux kernel amdgpu: recursive reservation lock in devcoredump can self-deadlock the coredump workerCVE-2026-80919 · Linux kernel amdgpu (devcoredump IB capture)Unscored
- Linux kernel nouveau: use-after-free racing the GEM info ioctl against GEM closeCVE-2026-89553 · Linux kernel nouveau GEM (info ioctl VMA lookup)Unscored
- Linux amdgpu: resume force-completes an uninitialized UVD ring on SR-IOV virtual functionsCVE-2026-89827 · Linux kernel amdgpu (UVD ring fence restore under SR-IOV)Unscored
- Linux amdgpu powerplay: malformed VBIOS VoltageObjectInfo table causes infinite loop or heap OOB readCVE-2026-93179 · Linux kernel drm/amd/powerplay (VoltageObjectInfo VBIOS table parser)Unscored
- Linux kernel amdgpu: use of freed module text when RCU callbacks run after module unloadCVE-2026-93809 · Linux kernel amdgpu (missing rcu_barrier() on module unload)Unscored
- Linux kernel amdkfd: user-controlled metadata size lets any render-group user force a huge kernel allocationCVE-2026-93823 · Linux kernel amdkfd (AMDKFD_IOC_GET_DMABUF_INFO metadata buffer)Unscored
This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.