Linux kernel null pointer access in AMD KFD CRIU queue restore
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.12.1116.18.537.2In the Linux kernel, the following vulnerability has been resolved:
drm/amdkfd: Properly acquire queue buffers in CRIU restore
When kfd_queue_acquire_buffers() was split off from set_queue_properties_from_user(), set_queue_properties_from_criu() was missed. Thus, set_queue_properties_from_criu() is not filling out the buffer fields of queue_properties, which can come up when subsequent code expects them to be non-null.
Add the proper call to kfd_queue_acquire_buffers(), and also use the right cast types in set_queue_properties_from_criu() (which were missed at the same time)
(cherry picked from commit 88ed96abbbe27b70193544fbc1ee06448c274714)
From the CVE record · Linux
During CRIU restore, the Linux kernel’s drm/amdkfd code can leave queue buffer fields unset. Subsequent code may encounter null fields where it expects buffers. The input does not specify attacker access requirements or whether user interaction is needed.
Engineers running Linux kernels that include drm/amdkfd should check their version against the vendor advisory; affected versions are not specified.