CVE-2021-47617
CVE.org · Published
- Record status
- Published
- Identifier year (not publication year)
- 2021
- Source publication
- Source updated
- Imported by cveboard
- Source snapshot
- cve_2026-10-24_midnight_baseline ·
CNA source text (English)
PCI: pciehp: Fix infinite loop in IRQ handler upon power fault
In the Linux kernel, the following vulnerability has been resolved: PCI: pciehp: Fix infinite loop in IRQ handler upon power fault The Power Fault Detected bit in the Slot Status register differs from all other hotplug events in that it is sticky: It can only be cleared after turning off slot power. Per PCIe r5.0, sec. 6.7.1.8: If a power controller detects a main power fault on the hot-plug slot, it must automatically set its internal main power fault latch [...]. The main power fault latch is cleared when software turns off power to the hot-plug slot. The stickiness used to cause interrupt storms and infinite loops which were fixed in 2009 by commits 5651c48cfafe ("PCI pciehp: fix power fault interrupt storm problem") and 99f0169c17f3 ("PCI: pciehp: enable software notification on empty slots"). Unfortunately in 2020 the infinite loop issue was inadvertently reintroduced by commit 8edf5332c393 ("PCI: pciehp: Fix MSI interrupt race"): The hardirq handler pciehp_isr() clears the PFD bit until pciehp's power_fault_detected flag is set. That happens in the IRQ thread pciehp_ist(), which never learns of the event because the hardirq handler is stuck in an infinite loop. Fix by setting the power_fault_detected flag already in the hardirq handler.
Scoped product and version facts
Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.
Exploitation unknown; this catalogue does not assess exploitation.
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
unaffected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| a8cc52270f3d8e8f4faf01ffd6c4a95bbfb55ba4 | affected | git | ff27f7d0333cff89ec85c419f431aca1b38fb16a | Unavailable | None listed |
| 4667358dab9cc07da044d5bc087065545b1000df | affected | git | 464da38ba827f670deac6500a1de9a4f0f44c41d | Unavailable | None listed |
| 8edf5332c39340b9583cf9cba659eb7ec71f75b5 | affected | git | 3b4c966fb156ff3e70b2526d964952ff7c1574d9 | Unavailable | None listed |
| 8edf5332c39340b9583cf9cba659eb7ec71f75b5 | affected | git | 1db58c6584a72102e98af2e600ea184ddaf2b8af | Unavailable | None listed |
| 8edf5332c39340b9583cf9cba659eb7ec71f75b5 | affected | git | 6d6f1f0dac3e3441ecdb1103d4efb11b9ed24dd5 | Unavailable | None listed |
| 8edf5332c39340b9583cf9cba659eb7ec71f75b5 | affected | git | 23584c1ed3e15a6f4bfab8dc5a88d94ab929ee12 | Unavailable | None listed |
| 4.19.149 | affected | semver | 4.19.233 | Unavailable | None listed |
| 5.4.69 | affected | semver | 5.4.177 | Unavailable | None listed |
Linux
- Vendor
- Linux
- Product
- Linux
- Platforms
- Unknown
- Default status
affected
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| 5.7 | affected | Unavailable | Unavailable | Unavailable | None listed |
| 0 | unaffected | semver | 5.7 | Unavailable | None listed |
| 4.19.233 | unaffected | semver | Unavailable | 4.19.* | None listed |
| 5.4.177 | unaffected | semver | Unavailable | 5.4.* | None listed |
| 5.10.97 | unaffected | semver | Unavailable | 5.10.* | None listed |
| 5.15.20 | unaffected | semver | Unavailable | 5.15.* | None listed |
| 5.16.6 | unaffected | semver | Unavailable | 5.16.* | None listed |
| 5.17 | unaffected | original_commit_for_fix | Unavailable | * | None listed |