CVE-2021-47617
published 2024-06-20CVE-2021-47617: 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…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.21%
11.3th percentile
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.
Affected
19 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.16.7-1 (bookworm) | linux 5.16.7-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 4.19.149 < 4.19.233 | 4.19.233 |
| linux | linux | >= 4667358dab9cc07da044d5bc087065545b1000df < 464da38ba827f670deac6500a1de9a4f0f44c41d | 464da38ba827f670deac6500a1de9a4f0f44c41d |
| linux | linux | >= 5.4.69 < 5.4.177 | 5.4.177 |
| linux | linux | >= 8edf5332c39340b9583cf9cba659eb7ec71f75b5 < 3b4c966fb156ff3e70b2526d964952ff7c1574d9 | 3b4c966fb156ff3e70b2526d964952ff7c1574d9 |
| linux | linux | >= 8edf5332c39340b9583cf9cba659eb7ec71f75b5 < 1db58c6584a72102e98af2e600ea184ddaf2b8af | 1db58c6584a72102e98af2e600ea184ddaf2b8af |
| linux | linux | >= 8edf5332c39340b9583cf9cba659eb7ec71f75b5 < 6d6f1f0dac3e3441ecdb1103d4efb11b9ed24dd5 | 6d6f1f0dac3e3441ecdb1103d4efb11b9ed24dd5 |
| linux | linux | >= 8edf5332c39340b9583cf9cba659eb7ec71f75b5 < 23584c1ed3e15a6f4bfab8dc5a88d94ab929ee12 | 23584c1ed3e15a6f4bfab8dc5a88d94ab929ee12 |
| linux | linux | >= a8cc52270f3d8e8f4faf01ffd6c4a95bbfb55ba4 < ff27f7d0333cff89ec85c419f431aca1b38fb16a | ff27f7d0333cff89ec85c419f431aca1b38fb16a |
| linux | linux_kernel | >= 0 < 5.10.103-1 | 5.10.103-1 |
| linux | linux_kernel | >= 0 < 5.16.7-1 | 5.16.7-1 |
| linux | linux_kernel | >= 0 < 5.16.7-1 | 5.16.7-1 |
| linux | linux_kernel | >= 0 < 5.16.7-1 | 5.16.7-1 |
| linux | linux_kernel | >= 4.19.149 < 4.19.233 | 4.19.233 |
| linux | linux_kernel | >= 5.11 < 5.15.20 | 5.15.20 |
| linux | linux_kernel | >= 5.16 < 5.16.6 | 5.16.6 |
| linux | linux_kernel | >= 5.4.69 < 5.4.177 | 5.4.177 |
| linux | linux_kernel | >= 5.7 < 5.10.97 | 5.10.97 |
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: PCI: pciehp: Fix infinite loop in IRQ handler upon power fault
vendor_redhat·2024-06-20·CVSS 5.5
CVE-2021-47617 [MEDIUM] CWE-835 kernel: PCI: pciehp: Fix infinite loop in IRQ handler upon power fault
kernel: 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"
Debian
CVE-2021-47617: linux - In the Linux kernel, the following vulnerability has been resolved: PCI: pciehp...
vendor_debian·2021·CVSS 5.5
CVE-2021-47617 [MEDIUM] CVE-2021-47617: linux - In the Linux kernel, the following vulnerability has been resolved: PCI: pciehp...
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
GHSA
GHSA-r68c-p976-5jmg: In the Linux kernel, the following vulnerability has been resolved:
PCI: pciehp: Fix infinite loop in IRQ handler upon power fault
The Power Fault D
ghsa_unreviewed·2024-06-20
CVE-2021-47617 [MEDIUM] CWE-835 GHSA-r68c-p976-5jmg: In the Linux kernel, the following vulnerability has been resolved:
PCI: pciehp: Fix infinite loop in IRQ handler upon power fault
The Power Fault D
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 em
OSV
CVE-2021-47617: In the Linux kernel, the following vulnerability has been resolved: PCI: pciehp: Fix infinite loop in IRQ handler upon power fault The Power Fault Det
osv·2024-06-20·CVSS 5.5
CVE-2021-47617 [MEDIUM] CVE-2021-47617: In the Linux kernel, the following vulnerability has been resolved: PCI: pciehp: Fix infinite loop in IRQ handler upon power fault The Power Fault Det
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
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://git.kernel.org/stable/c/1db58c6584a72102e98af2e600ea184ddaf2b8afhttps://git.kernel.org/stable/c/23584c1ed3e15a6f4bfab8dc5a88d94ab929ee12https://git.kernel.org/stable/c/3b4c966fb156ff3e70b2526d964952ff7c1574d9https://git.kernel.org/stable/c/464da38ba827f670deac6500a1de9a4f0f44c41dhttps://git.kernel.org/stable/c/6d6f1f0dac3e3441ecdb1103d4efb11b9ed24dd5https://git.kernel.org/stable/c/ff27f7d0333cff89ec85c419f431aca1b38fb16ahttps://git.kernel.org/stable/c/1db58c6584a72102e98af2e600ea184ddaf2b8afhttps://git.kernel.org/stable/c/23584c1ed3e15a6f4bfab8dc5a88d94ab929ee12https://git.kernel.org/stable/c/3b4c966fb156ff3e70b2526d964952ff7c1574d9https://git.kernel.org/stable/c/464da38ba827f670deac6500a1de9a4f0f44c41dhttps://git.kernel.org/stable/c/6d6f1f0dac3e3441ecdb1103d4efb11b9ed24dd5https://git.kernel.org/stable/c/ff27f7d0333cff89ec85c419f431aca1b38fb16a
2024-06-20
Published