Skip to main content
VulnerabilityPublished Updated

CVE-2025-37843: Linux kernel · PCI: pciehp: Avoid unnecessary device replacement check

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-37843· Medium

Not known to be exploited · CVSS 5.5 Medium.

Data as of 13 Nov 2026, 19:21 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 May 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

AI-suggested

The vendor has resolved this vulnerability with a kernel patch that avoids unnecessary device replacement checks when a hotplug port itself was removed, preventing the deadlock. Users should apply the official Linux kernel updates containing this fix once available. No other mitigation or workaround is indicated.

Description

CVE-2025-37843 is a medium-severity vulnerability in the Linux kernel's PCI hotplug (pciehp) subsystem. It involves a race condition during hot-removal of nested PCI hotplug ports that can cause a deadlock. The issue arises when a parent hotplug port holds a lock and waits for a child port to unbind, while the child simultaneously tries to acquire the same lock to remove its children. This deadlock is triggered more frequently by a recent kernel commit related to device replacement detection during system sleep. The fix avoids unnecessary device replacement checks when a hotplug port itself was removed, preventing the deadlock scenario.

References

Community reviews

Loading reviews…