Heimdall Security Logo

CVE-2021-47617

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : <3b4c966fb156ff3e70b2526d964952ff7c1574d9, <23584c1ed3e15a6f4bfab8dc5a88d94ab929ee12, 4.19.233, <1db58c6584a72102e98af2e600ea184ddaf2b8af, <4.19.233, 0, 4.19.149, 8edf5332c39340b9583cf9cba659eb7ec71f75b5, <5.7, <=5.10.*, 5.4.69, 4667358dab9cc07da044d5bc087065545b1000df, 5.16.6, <=5.4.*, <=4.19.*, a8cc52270f3d8e8f4faf01ffd6c4a95bbfb55ba4, <ff27f7d0333cff89ec85c419f431aca1b38fb16a, 5.10.97, <5.4.177, <=5.16.*, 5.15.20, <6d6f1f0dac3e3441ecdb1103d4efb11b9ed24dd5, 5.7, <=*, <=5.15.*, 5.17, 5.4.177, <464da38ba827f670deac6500a1de9a4f0f44c41d

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.

Gravité et risque d'exploitation

CVE-2021-47617 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.21 %, ce qui la place devant 10.7 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <3b4c966fb156ff3e70b2526d964952ff7c1574d9, <23584c1ed3e15a6f4bfab8dc5a88d94ab929ee12, 4.19.233, <1db58c6584a72102e98af2e600ea184ddaf2b8af, <4.19.233, 0, 4.19.149, 8edf5332c39340b9583cf9cba659eb7ec71f75b5, <5.7, <=5.10.*, 5.4.69, 4667358dab9cc07da044d5bc087065545b1000df, 5.16.6, <=5.4.*, <=4.19.*, a8cc52270f3d8e8f4faf01ffd6c4a95bbfb55ba4, <ff27f7d0333cff89ec85c419f431aca1b38fb16a, 5.10.97, <5.4.177, <=5.16.*, 5.15.20, <6d6f1f0dac3e3441ecdb1103d4efb11b9ed24dd5, 5.7, <=*, <=5.15.*, 5.17, 5.4.177, <464da38ba827f670deac6500a1de9a4f0f44c41d) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

Rechercher une autre CVE