{
  "cveId": "CVE-2021-47617",
  "url": "https://patchblox.com/security/cve/CVE-2021-47617",
  "summary": "CVE-2021-47617 is fixed in linux on 1 platform, first by DEBIAN-CVE-2021-47617, released June 20, 2024. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  PCI: pciehp: Fix infinite loop in IRQ handler up...",
  "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 (\u0022PCI pciehp: fix power fault interrupt storm problem\u0022) and 99f0169c17f3 (\u0022PCI: pciehp: enable software notification on empty slots\u0022).  Unfortunately in 2020 the infinite loop issue was inadvertently reintroduced by commit 8edf5332c393 (\u0022PCI: pciehp: Fix MSI interrupt race\u0022):  The hardirq handler pciehp_isr() clears the PFD bit until pciehp\u0027s 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.",
  "published": "2024-06-20T11:15:54Z",
  "severity": "medium",
  "cvss": 5.5,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "epss": 0.0021,
  "epssPercentile": 0.11318,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "5.16.7-1",
      "fix": "DEBIAN-CVE-2021-47617",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2021-47617",
      "released": "2024-06-20T11:15:54Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "5.16.7-1",
      "fix": "DEBIAN-CVE-2021-47617",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2021-47617",
      "released": "2024-06-20T11:15:54Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "5.16.7-1",
      "fix": "DEBIAN-CVE-2021-47617",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2021-47617",
      "released": "2024-06-20T11:15:54Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-09T01:18:40Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}