CVE-2025-37843 Details
Description
In the Linux kernel, the following vulnerability has been resolved: PCI: pciehp: Avoid unnecessary device replacement check Hot-removal of nested PCI hotplug ports suffers from a long-standing race condition which can lead to a deadlock: A parent hotplug port acquires pci_lock_rescan_remove(), then waits for pciehp to unbind from a child hotplug port. Meanwhile that child hotplug port tries to acquire pci_lock_rescan_remove() as well in order to remove its own children. The deadlock only occurs if the parent acquires pci_lock_rescan_remove() first, not if the child happens to acquire it first. Several workarounds to avoid the issue have been proposed and discarded over the years, e.g.: https://lore.kernel.org/r/4c882e25194ba8282b78fe963fec8faae7cf23eb.1529173804.git.lukas@wunner.de/ A proper fix is being worked on, but needs more time as it is nontrivial and necessarily intrusive. Recent commit 9d573d19547b ("PCI: pciehp: Detect device replacement during system sleep") provokes more frequent occurrence of the deadlock when removing more than one Thunderbolt device during system sleep. The commit sought to detect device replacement, but also triggered on device removal. Differentiating reliably between replacement and removal is impossible because pci_get_dsn() returns 0 both if the device was removed, as well as if it was replaced with one lacking a Device Serial Number. Avoid the more frequent occurrence of the deadlock by checking whether the hotplug port itself was hot-removed. If so, there's no sense in checking whether its child device was replaced. This works because the ->resume_noirq() callback is invoked in top-down order for the entire hierarchy: A parent hotplug port detecting device replacement (or removal) marks all children as removed using pci_dev_set_disconnected() and a child hotplug port can then reliably detect being removed.
A deadlock vulnerability has been identified in the Linux kernel's PCI hotplug port management. This issue arises during the hot-removal of nested PCI hotplug ports, creating a race condition that can lead to a deadlock situation. The problem occurs when a parent hotplug port acquires a lock to manage device removal, while simultaneously waiting for a child hotplug port to unbind. The child, in turn, attempts to acquire the same lock to remove its own devices, leading to a deadlock. This vulnerability is exacerbated by recent changes that increase the frequency of such deadlocks when multiple Thunderbolt devices are removed during system sleep.
A recent commit has been made to address this vulnerability by avoiding unnecessary checks for device replacement on hotplug ports that have already been removed. This fix is included in the latest stable version of the Linux kernel.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Nov 5, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/0d0bbd01f7c0ac7d1be9f85aaf2cd0baec34655f | kernel.org | Patch |
| https://git.kernel.org/stable/c/7535d10a2c61baeff493300070cf04d9ddda216b | kernel.org | Patch |
| https://git.kernel.org/stable/c/e3260237aaadc9799107ccb940c6688195c4518d | kernel.org | Patch |
| https://git.kernel.org/stable/c/e4a1d7defbc2d806540720a5adebe24ec3488683 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-667 | Improper Locking | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.11, < 6.12.24 >= 6.13, < 6.13.12 >= 6.14, < 6.14.3 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 5, 2026 | CVE Modified | kernel.org |
| Nov 5, 2026 | CVE Modified | CISA-ADP |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 17, 2025 | Initial Analysis | [email protected] |
| May 9, 2025 | New CVE Received | kernel.org |