drm/amdgpu: Fix error handling in slot reset
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.18.176.19.77.0In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: Fix error handling in slot reset
If the device has not recovered after slot reset is called, it goes to out label for error handling. There it could make decision based on uninitialized hive pointer and could result in accessing an uninitialized list.
Initialize the list and hive properly so that it handles the error situation and also releases the reset domain lock which is acquired during error_detected callback.
(cherry picked from commit bb71362182e59caa227e4192da5a612b09349696)
From the CVE record · Linux
The Linux kernel's drm/amdgpu slot-reset error handling can use an uninitialized hive pointer and access an uninitialized list if the device fails to recover after a slot reset. The input does not establish whether an attacker can trigger this condition or specify network, authentication, or user-interaction requirements.
Engineers running Linux kernels with drm/amdgpu should check whether their kernel includes the fix; affected versions are not specified.