drm/amdgpu: handle the case of pci_channel_io_frozen only in amdgpu_pci_resume
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 |
|
|
5.10.2415.14.125.15In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: handle the case of pci_channel_io_frozen only in amdgpu_pci_resume
In current code, when a PCI error state pci_channel_io_normal is detectd, it will report PCI_ERS_RESULT_CAN_RECOVER status to PCI driver, and PCI driver will continue the execution of PCI resume callback report_resume by pci_walk_bridge, and the callback will go into amdgpu_pci_resume finally, where write lock is releasd unconditionally without acquiring such lock first. In this case, a deadlock will happen when other threads start to acquire the read lock.
To fix this, add a member in amdgpu_device strucutre to cache pci_channel_state, and only continue the execution in amdgpu_pci_resume when it's pci_channel_io_frozen.
From the CVE record · Linux
The Linux kernel’s amdgpu PCI resume callback can release a write lock it did not acquire when handling a normal PCI error state. Other threads trying to acquire the read lock can then deadlock. The input does not specify whether an attacker can trigger this condition or whether access or user interaction is required.
Engineers running Linux kernels with the amdgpu driver should check their versions; affected versions are not specified.