CVE-2021-47421
In 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…
Does this matter?
Lower severity and a low EPSS score (0.20%). Track it; it rarely justifies an emergency change on its own.
Description
In 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.
- CVSS 3.1
- 5.5 MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 0.20% probability · 11th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-667
- Affected
- linux/linux kernel
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
References
- https://git.kernel.org/stable/c/248b061689a40f4fed05252ee2c89f87cf26d7d8Patch
- https://git.kernel.org/stable/c/72e9a1bf9b722628c28092e0c2cd8717edd201dcPatch
- https://git.kernel.org/stable/c/785cc093b6b5a93cc350421a55f3f1eda6585156Patch
- https://git.kernel.org/stable/c/248b061689a40f4fed05252ee2c89f87cf26d7d8Patch
- https://git.kernel.org/stable/c/72e9a1bf9b722628c28092e0c2cd8717edd201dcPatch
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.