Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2021-47617: PCI: pciehp: Fix infinite loop in IRQ handler upon power fault

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 1db58c6584a72102e98af2e600ea184ddaf2b8af, 23584c1ed3e15a6f4bfab8dc5a88d94ab929ee12, 3b4c966fb156ff3e70b2526d964952ff7c1574d9.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 1db58c6584a72102e98af2e600ea184ddaf2b8af, 23584c1ed3e15a6f4bfab8dc5a88d94ab929ee12, 3b4c966fb156ff3e70b2526d964952ff7c1574d9 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jun 20, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 11th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2021-47617

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.19.149 and later · before 4.19.233
  • linux linux kernel5.4.69 and later · before 5.4.177
  • linux linux kernel5.7 and later · before 5.10.97
  • linux linux kernel5.11 and later · before 5.15.20
  • linux linux kernel5.16 and later · before 5.16.6

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.7affected
    • a8cc52270f3d8e8f4faf01ffd6c4a95bbfb55ba4 and later · before ff27f7d0333cff89ec85c419f431aca1b38fb16aaffected · git
    • 4667358dab9cc07da044d5bc087065545b1000df and later · before 464da38ba827f670deac6500a1de9a4f0f44c41daffected · git
    • 8edf5332c39340b9583cf9cba659eb7ec71f75b5 and later · before 3b4c966fb156ff3e70b2526d964952ff7c1574d9affected · git
    • 8edf5332c39340b9583cf9cba659eb7ec71f75b5 and later · before 1db58c6584a72102e98af2e600ea184ddaf2b8afaffected · git
    • 8edf5332c39340b9583cf9cba659eb7ec71f75b5 and later · before 6d6f1f0dac3e3441ecdb1103d4efb11b9ed24dd5affected · git
    • 8edf5332c39340b9583cf9cba659eb7ec71f75b5 and later · before 23584c1ed3e15a6f4bfab8dc5a88d94ab929ee12affected · git
    • 4.19.149 and later · before 4.19.233affected · semver
    • 5.4.69 and later · before 5.4.177affected · semver
    • before 5.7not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.16.7-15.16.7-1
SUSE:Linux Enterprise Micro 5.1kernel-rtbefore 5.3.18-150300.175.15.3.18-150300.175.1
SUSE:Linux Enterprise Micro 5.1kernel-source-rtbefore 5.3.18-150300.175.15.3.18-150300.175.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-38620Jun 20, 2024 · Bluetooth: HCI: Remove HCI_AMP support
    22Monitor
  • ← EarlierCVE-2024-38619Jun 20, 2024 · usb-storage: alauda: Check whether the media is initialized
    22Monitor
  • Later →CVE-2021-47618Jun 20, 2024 · ARM: 9170/1: fix panic when kasan and kprobe are enabled
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1db58c6584a72102e98af2e600ea184ddaf2b8afVendor (CNA)
Linux Linux23584c1ed3e15a6f4bfab8dc5a88d94ab929ee12Vendor (CNA)
Linux Linux3b4c966fb156ff3e70b2526d964952ff7c1574d9Vendor (CNA)
Linux Linux4.19.233Vendor (CNA)
Linux Linux464da38ba827f670deac6500a1de9a4f0f44c41dVendor (CNA)
Linux Linux5.4.177Vendor (CNA)
Linux Linux6d6f1f0dac3e3441ecdb1103d4efb11b9ed24dd5Vendor (CNA)
Linux Linuxff27f7d0333cff89ec85c419f431aca1b38fb16aVendor (CNA)
debian:linux5.16.7-1 · Debian:12Package registry (OSV)
suse:kernel-rt5.3.18-150300.175.1 · SUSE:Linux Enterprise Micro 5.1Package registry (OSV)
suse:kernel-source-rt5.3.18-150300.175.1 · SUSE:Linux Enterprise Micro 5.1Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2024-2703250 days apartf2fs: fix to avoid potential panic during recovery
    25Monitor
  • CVE-2022-4863553 days apartfsdax: Fix infinite loop in dax_iomap_rw()
    24Monitor
  • CVE-2024-362881 days apartSUNRPC: Fix loop termination condition in gss_free_in_token_pages()
    22Monitor
  • CVE-2024-4099522 days apartnet/sched: act_api: fix possible infinite loop in tcf_idr_check_alloc()
    22Monitor
  • CVE-2022-4878026 days apartnet/smc: Avoid overwriting the copies of clcsock callback functions
    22Monitor
  • CVE-2022-4886226 days apartvhost: fix hung thread due to erroneous iotlb entries
    22Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records