CVE-2026-99119unknown
drm/amdgpu/userq: actually validate userq BOs
Impact
In the Linux kernel, the following vulnerability has been resolved:
Source excerpt · LinuxAffected packages
This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
Linux · Linux
Other versions: unaffected
| Version / range | Source status |
|---|---|
| 4cdbba5a16aaf16513b69cc332b1d6f971a44b52 to before d1d6b859e89dd274cd0fae77503cdf91be8310c0 | affected |
| 4cdbba5a16aaf16513b69cc332b1d6f971a44b52 to before 32d0771ef4ca69c30a1db3aefa34dd177cd2a047 | affected |
Linux · Linux
Other versions: affected
| Version / range | Source status |
|---|---|
| 7.2 | affected |
| 0 to before 7.2 | unaffected |
| 7.2.13 through 7.2.* (inclusive) | unaffected |
| 7.3 through * (inclusive) | unaffected |
Original source description
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)