https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 21:17:23 +0000 https://cve.radiocsirt.org/vuln/bdu:2024-10971 bdu:2024-10971 https://cve.radiocsirt.org/vuln/bdu:2024-10971 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0578 certfr-2024-avi-0578 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0578 https://cve.radiocsirt.org/vuln/euvd-2026-320247 EUVD-2026-320247 https://cve.radiocsirt.org/vuln/euvd-2026-320247 https://cve.radiocsirt.org/vuln/fkie_cve-2021-47617 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>PCI: pciehp: Fix infinite loop in IRQ handler upon power fault</p> <p>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:</p> <p>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.</p> <p>The stickiness used to cause interrupt storms and infinite loops which were fixed in 2009 by commits 5651c48cfafe (&#34;PCI pciehp: fix power fault interrupt storm problem&#34;) and 99f0169c17f3 (&#34;PCI: pciehp: enable software notification on empty slots&#34;).</p> <p>Unfortunately in 2020 the infinite loop issue was inadvertently reintroduced by commit 8edf5332c393 (&#34;PCI: pciehp: Fix MSI interrupt race&#34;): The hardirq handler pciehp_isr() clears the PFD bit until pciehp&#39;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.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>PCI: pciehp: Fix infinite loop in IRQ handler upon power fault</p> <p>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:</p> <p>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.</p> <p>The stickiness used to cause interrupt storms and infinite loops which were fixed in 2009 by commits 5651c48cfafe (&#34;PCI pciehp: fix power fault interrupt storm problem&#34;) and 99f0169c17f3 (&#34;PCI: pciehp: enable software notification on empty slots&#34;).</p> <p>Unfortunately in 2020 the infinite loop issue was inadvertently reintroduced by commit 8edf5332c393 (&#34;PCI: pciehp: Fix MSI interrupt race&#34;): The hardirq handler pciehp_isr() clears the PFD bit until pciehp&#39;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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2021-47617 https://cve.radiocsirt.org/vuln/ghsa-r68c-p976-5jmg <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>PCI: pciehp: Fix infinite loop in IRQ handler upon power fault</p> <p>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:</p> <p>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.</p> <p>The stickiness used to cause interrupt storms and infinite loops which were fixed in 2009 by commits 5651c48cfafe (&#34;PCI pciehp: fix power fault interrupt storm problem&#34;) and 99f0169c17f3 (&#34;PCI: pciehp: enable software notification on empty slots&#34;).</p> <p>Unfortunately in 2020 the infinite loop issue was inadvertently reintroduced by commit 8edf5332c393 (&#34;PCI: pciehp: Fix MSI interrupt race&#34;): The hardirq handler pciehp_isr() clears the PFD bit until pciehp&#39;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.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>PCI: pciehp: Fix infinite loop in IRQ handler upon power fault</p> <p>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:</p> <p>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.</p> <p>The stickiness used to cause interrupt storms and infinite loops which were fixed in 2009 by commits 5651c48cfafe (&#34;PCI pciehp: fix power fault interrupt storm problem&#34;) and 99f0169c17f3 (&#34;PCI: pciehp: enable software notification on empty slots&#34;).</p> <p>Unfortunately in 2020 the infinite loop issue was inadvertently reintroduced by commit 8edf5332c393 (&#34;PCI: pciehp: Fix MSI interrupt race&#34;): The hardirq handler pciehp_isr() clears the PFD bit until pciehp&#39;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.</p> https://cve.radiocsirt.org/vuln/ghsa-r68c-p976-5jmg https://cve.radiocsirt.org/vuln/suse-su-2024:2360-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2024:2360-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47617 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-gcp-5.4, Ubuntu:18.04:LTS: linux-hwe-5.4, Ubuntu:18.04:LTS: linux-ibm-5.4, Ubuntu:18.04:LTS: linux-oracle-5.4, Ubuntu:18.04:LTS: linux-raspi-5.4, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3 and 80 more</p> <p>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 (&#34;PCI pciehp: fix power fault interrupt storm problem&#34;) and 99f0169c17f3 (&#34;PCI: pciehp: enable software notification on empty slots&#34;). Unfortunately in 2020 the infinite loop issue was inadvertently reintroduced by commit 8edf5332c393 (&#34;PCI: pciehp: Fix MSI interrupt race&#34;): The hardirq handler pciehp_isr() clears the PFD bit until pciehp&#39;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.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-gcp-5.4, Ubuntu:18.04:LTS: linux-hwe-5.4, Ubuntu:18.04:LTS: linux-ibm-5.4, Ubuntu:18.04:LTS: linux-oracle-5.4, Ubuntu:18.04:LTS: linux-raspi-5.4, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3 and 80 more</p> <p>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 (&#34;PCI pciehp: fix power fault interrupt storm problem&#34;) and 99f0169c17f3 (&#34;PCI: pciehp: enable software notification on empty slots&#34;). Unfortunately in 2020 the infinite loop issue was inadvertently reintroduced by commit 8edf5332c393 (&#34;PCI: pciehp: Fix MSI interrupt race&#34;): The hardirq handler pciehp_isr() clears the PFD bit until pciehp&#39;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.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47617 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1418 <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1418