drm/amdkfd: fix QID bit leak in pqm_create_queue()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
9d61e2b81f5fc90c87975879809346e7c90ea5f9| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/amdkfd: fix QID bit leak in pqm_create_queue()
When MES is enabled and amdgpu_amdkfd_alloc_kernel_mem() fails during the first queue creation for a process, pqm_create_queue() returns early via 'return retval' without going through the err_create_queue cleanup label.
This means clear_bit(*qid, pqm->queue_slot_bitmap) is never called, leaving the reserved QID bit permanently set in queue_slot_bitmap. Over time this leaks QID slots, potentially exhausting all available queue slots.
Fix this by replacing 'return retval' with 'goto err_allocate_pqn' so that clear_bit() is always called on the error path without touching the uninitialized pqn pointer.
AILIKFD-813
(cherry picked from commit a107f74c38edbb80d6ab64dcaeeb292c14e9779f)
From the CVE record · Linux
The Linux kernel's drm/amdkfd queue creation path can leave a QID slot reserved if MES is enabled and kernel memory allocation fails during a process's first queue creation. Repeated failures can exhaust available queue slots. The input does not specify an attacker-controlled trigger or authentication requirements.
Operators running Linux kernels with drm/amdkfd and MES enabled should check their kernel; affected versions are not specified.