CVE-2021-47421
published 2024-05-21CVE-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…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.20%
10.5th percentile
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
15 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.14.12-1 (bookworm) | linux 5.14.12-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= c9a6b82f45e261d247b980a7949aaa6a9bfffe01 < 785cc093b6b5a93cc350421a55f3f1eda6585156 | 785cc093b6b5a93cc350421a55f3f1eda6585156 |
| linux | linux | >= c9a6b82f45e261d247b980a7949aaa6a9bfffe01 < 72e9a1bf9b722628c28092e0c2cd8717edd201dc | 72e9a1bf9b722628c28092e0c2cd8717edd201dc |
| linux | linux | >= c9a6b82f45e261d247b980a7949aaa6a9bfffe01 < 248b061689a40f4fed05252ee2c89f87cf26d7d8 | 248b061689a40f4fed05252ee2c89f87cf26d7d8 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.244-1 | 5.10.244-1 |
| linux | linux_kernel | >= 0 < 5.14.12-1 | 5.14.12-1 |
| linux | linux_kernel | >= 0 < 5.14.12-1 | 5.14.12-1 |
| linux | linux_kernel | >= 0 < 5.14.12-1 | 5.14.12-1 |
| linux | linux_kernel | >= 5.10 < 5.10.241 | 5.10.241 |
| linux | linux_kernel | >= 5.11 < 5.14.12 | 5.14.12 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: drm/amdgpu: handle the case of pci_channel_io_frozen only in amdgpu_pci_resume
vendor_redhat·2024-05-21·CVSS 5.5
CVE-2021-47421 [MEDIUM] CWE-667 kernel: drm/amdgpu: handle the case of pci_channel_io_frozen only in amdgpu_pci_resume
kernel: drm/amdgpu: handle the case of pci_channel_io_frozen only in amdgpu_pci_resume
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
Debian
CVE-2021-47421: linux - In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu:...
vendor_debian·2021·CVSS 5.5
CVE-2021-47421 [MEDIUM] CVE-2021-47421: linux - In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu:...
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.
Scope: local
bookworm: r
GHSA
GHSA-pxqq-3ph7-mw6w: 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
I
ghsa_unreviewed·2024-05-21
CVE-2021-47421 [MEDIUM] CWE-667 GHSA-pxqq-3ph7-mw6w: 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
I
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.
OSV
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
osv·2024-05-21·CVSS 5.5
CVE-2021-47421 [MEDIUM] 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
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.
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/248b061689a40f4fed05252ee2c89f87cf26d7d8https://git.kernel.org/stable/c/72e9a1bf9b722628c28092e0c2cd8717edd201dchttps://git.kernel.org/stable/c/785cc093b6b5a93cc350421a55f3f1eda6585156https://git.kernel.org/stable/c/248b061689a40f4fed05252ee2c89f87cf26d7d8https://git.kernel.org/stable/c/72e9a1bf9b722628c28092e0c2cd8717edd201dchttps://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
2024-05-21
Published