PT-2026-152510

CVE-2026-99630

·

Published

2026-11-20

·

Updated

2026-11-20

Description by

Score
N/A
Not available

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.

In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu/userq: validate the moved individual BOs on restore
An individual BO of a user queue VM, i.e. one which doesn't share the root reservation, goes to the individual needs update list when it is evicted. The user queue restore looked at vm->invalidated for them, which the VM state machine rework turned into the always valid evicted list and commit 18decfc9e8cc ("drm/amdgpu/userq: actually validate userq BOs") into the individual evicted one. That list only holds imported DMA-bufs of compute VMs though, so for a user queue VM nothing is validated.
The restore then neither locks such a BO nor moves it back. Its PTEs are updated to wherever it is now, cleared if it went to system memory, and it doesn't get the new eviction fence, so it can move again under the running queue.
On navi48, once the BOs of an SDMA user queue are evicted from GTT (debugfs amdgpu evict gtt) the queue faults on its ring and rptr:
amdgpu 0000:03:00.0: in page starting at address 0x0000000100000000 from client 10 amdgpu 0000:03:00.0: Faulty UTCL2 client ID: SDMA0 (0xd) amdgpu 0000:03:00.0: in page starting at address 0x0000000100101000 from client 10
Validate the BOs on the individual needs update list like before.
(cherry picked from commit eb0d94765d4be18d41e93ad09947dd9cc06ed31a)
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾