Live › vulnerability › CVE-2026-99119
Go to dashboardIn the Linux kernel's AMD GPU (amdgpu) user queue code, buffer objects that were evicted before a user queue was created are not properly validated, so they never get an eviction fence re-armed. The sources do not state what an attacker gains from this beyond the fix description.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 11:32 UTC. All times on this page are UTC.
Systems running a Linux kernel with the amdgpu driver and user queues enabled, which is typical of AMD GPU hosts. The sources do not say which configurations or workloads trigger the flaw, so unknown whether systems without AMD GPUs or without user queues can skip it.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu/userq: actually validate userq BOs
This was supposed to loop over the individual evicted list, as the kernel and always_valid evicted lists were already handled in amdgpu_vm_validate.
Without this, BOs that were created and evicted before a userq was made would never end up in an eviction fence rearm.
Also add the missing ref to the BO before drm_exec locks and refs it.
(cherry picked from commit 18decfc9e8cc0fa70b6de9944cc27a37729edfbd)
This page as .md · .json · in your agent: get_signal("CVE-2026-99119")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.