drm/amdkfd: Check bounds for allocate_sdma_queue restore_sdma_id
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/amdkfd: Check bounds for allocate_sdma_queue restore_sdma_id
allocate_sdma_queue has an option where the sdma queue id can be specified (used by CRIU). We weren't bounds-checking that value.
Confirm it's less than the maximum number of queues.
From the CVE record · Linux
The Linux kernel's drm/amdkfd allocate_sdma_queue function did not check the bounds of a specified SDMA queue ID. This could allow an ID at or above the maximum number of queues when the restore_sdma_id option is used by CRIU. The input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels with drm/amdkfd should check their versions; affected versions are not specified.