CVEvulnerability
CVE-2021-47421
5.5 MEDIUM
Official page ↗
- Status
- Modified
- Published
- 2024-05-21
- Last modified
- 2026-08-04
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
- 7.8 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CVSS 3.1 ([email protected])
- 5.5 MEDIUM — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weaknesses
- CWE-667
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.
Affected configurations
• linux linux kernel (>= 5.10 < 5.10.241)
• linux linux kernel (>= 5.11 < 5.14.12)
• linux linux kernel 5.15
Related
Weakness · CWE (1)
- CWE-667 Improper Locking weakness
References
- https://git.kernel.org/stable/c/248b061689a40f4fed05252ee2c89f87cf26d7d8 Patch
- https://git.kernel.org/stable/c/72e9a1bf9b722628c28092e0c2cd8717edd201dc Patch
- https://git.kernel.org/stable/c/785cc093b6b5a93cc350421a55f3f1eda6585156 Patch
- https://git.kernel.org/stable/c/248b061689a40f4fed05252ee2c89f87cf26d7d8 Patch
- https://git.kernel.org/stable/c/72e9a1bf9b722628c28092e0c2cd8717edd201dc Patch
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html lists.debian.org