CVE-2021-47617
"PCIe_hp Infinite Loop Vulnerability"
Description
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.
INFO
Published Date :
June 20, 2024, 11:15 a.m.
Last Modified :
Nov. 21, 2024, 6:36 a.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
3.6
Exploitability Score :
1.8
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2021-47617.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2021-47617 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2021-47617 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/1db58c6584a72102e98af2e600ea184ddaf2b8af Added Reference https://git.kernel.org/stable/c/23584c1ed3e15a6f4bfab8dc5a88d94ab929ee12 Added Reference https://git.kernel.org/stable/c/3b4c966fb156ff3e70b2526d964952ff7c1574d9 Added Reference https://git.kernel.org/stable/c/464da38ba827f670deac6500a1de9a4f0f44c41d Added Reference https://git.kernel.org/stable/c/6d6f1f0dac3e3441ecdb1103d4efb11b9ed24dd5 Added Reference https://git.kernel.org/stable/c/ff27f7d0333cff89ec85c419f431aca1b38fb16a -
Initial Analysis by [email protected]
Sep. 18, 2024
Action Type Old Value New Value Added CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Changed Reference Type https://git.kernel.org/stable/c/1db58c6584a72102e98af2e600ea184ddaf2b8af No Types Assigned https://git.kernel.org/stable/c/1db58c6584a72102e98af2e600ea184ddaf2b8af Patch Changed Reference Type https://git.kernel.org/stable/c/23584c1ed3e15a6f4bfab8dc5a88d94ab929ee12 No Types Assigned https://git.kernel.org/stable/c/23584c1ed3e15a6f4bfab8dc5a88d94ab929ee12 Patch Changed Reference Type https://git.kernel.org/stable/c/3b4c966fb156ff3e70b2526d964952ff7c1574d9 No Types Assigned https://git.kernel.org/stable/c/3b4c966fb156ff3e70b2526d964952ff7c1574d9 Patch Changed Reference Type https://git.kernel.org/stable/c/464da38ba827f670deac6500a1de9a4f0f44c41d No Types Assigned https://git.kernel.org/stable/c/464da38ba827f670deac6500a1de9a4f0f44c41d Patch Changed Reference Type https://git.kernel.org/stable/c/6d6f1f0dac3e3441ecdb1103d4efb11b9ed24dd5 No Types Assigned https://git.kernel.org/stable/c/6d6f1f0dac3e3441ecdb1103d4efb11b9ed24dd5 Patch Changed Reference Type https://git.kernel.org/stable/c/ff27f7d0333cff89ec85c419f431aca1b38fb16a No Types Assigned https://git.kernel.org/stable/c/ff27f7d0333cff89ec85c419f431aca1b38fb16a Patch Added CWE NIST CWE-835 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.19.149 up to (excluding) 4.19.233 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.4.69 up to (excluding) 5.4.177 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.7 up to (excluding) 5.10.97 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.20 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 5.16.6 -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jun. 20, 2024
Action Type Old Value New Value Added Description 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. Added Reference kernel.org https://git.kernel.org/stable/c/ff27f7d0333cff89ec85c419f431aca1b38fb16a [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/464da38ba827f670deac6500a1de9a4f0f44c41d [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/3b4c966fb156ff3e70b2526d964952ff7c1574d9 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/1db58c6584a72102e98af2e600ea184ddaf2b8af [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/6d6f1f0dac3e3441ecdb1103d4efb11b9ed24dd5 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/23584c1ed3e15a6f4bfab8dc5a88d94ab929ee12 [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2021-47617 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2021-47617
weaknesses.