CVE-2025-38624: PCI: pnv_php: Clean up allocated IRQs on unplug
In the Linux kernel, the following vulnerability has been resolved:
PCI: pnv_php: Clean up allocated IRQs on unplug
When the root of a nested PCIe bridge configuration is unplugged, the
pnv_php driver leaked the allocated IRQ resources for the child bridges'
hotplug event notifications, resulting in a panic.
Fix this by walking all child buses and deallocating all its IRQ resources
before calling pci_hp_remove_devices().
Also modify the lifetime of the workqueue at struct pnv_php_slot::wq so
that it is only destroyed in pnv_php_free_slot(), instead of
pnv_php_disable_irq(). This is required since pnv_php_disable_irq() will
now be called by workers triggered by hot unplug interrupts, so the
workqueue needs to stay allocated.
The abridged kernel panic that occurs without this patch is as follows:
WARNING: CPU: 0 PID: 687 at kernel/irq/msi.c:292 msi_device_data_release+0x6c/0x9c
CPU: 0 UID: 0 PID: 687 Comm: bash Not tainted 6.14.0-rc5+ #2
Call Trace:
msi_device_data_release+0x34/0x9c (unreliable)
release_nodes+0x64/0x13c
devres_release_all+0xc0/0x140
device_del+0x2d4/0x46c
pci_destroy_dev+0x5c/0x194
pci_hp_remove_devices+0x90/0x128
pci_hp_remove_devices+0x44/0x128
pnv_php_disable_slot+0x54/0xd4
power_write_file+0xf8/0x18c
pci_slot_attr_store+0x40/0x5c
sysfs_kf_write+0x64/0x78
kernfs_fop_write_iter+0x1b0/0x290
vfs_write+0x3bc/0x50c
ksys_write+0x84/0x140
system_call_exception+0x124/0x230
system_call_vectored_common+0x15c/0x2ec
[bhelgaas: tidy comments]
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash a system during certain PCIe hot-unplug operations. It is not described as remote code execution or data theft. Business risk is availability: affected servers using this PCI hotplug path may panic when nested PCIe bridge hardware is unplugged or removed.
Executive priority
Treat as a targeted availability risk, not a broad internet-facing emergency. Prioritize patching for Linux servers where PCIe hotplug is used or hardware maintenance is frequent. For ordinary systems without this driver path, routine kernel update cadence is likely sufficient.
Technical view
In the pnv_php PCI hotplug driver, IRQ resources for child bridge hotplug notifications were not freed before device removal. When the root of a nested PCIe bridge configuration is unplugged, the leak can trigger a kernel panic. The upstream fix walks child buses, deallocates IRQ resources, and adjusts workqueue lifetime handling.
Likely exposure
Exposure appears narrow: Linux systems using the pnv_php PCI hotplug driver with nested PCIe bridge configurations. The CVE record lists Linux kernel versions across multiple stable lines as affected and provides stable kernel fix commits. Confirm actual exposure through kernel version, distro backports, and whether this driver/hardware path is present.
Exploitation context
No CISA KEV listing is provided, and the sources do not state active exploitation. The described trigger is a hot-unplug/remove scenario, including sysfs-driven slot power handling and hot-unplug interrupts. Practical exploitation likely requires local administrative or physical/control-plane ability to trigger relevant PCIe hotplug behavior.
Researcher notes
The public record lacks CVSS, CWE, and detailed product matrix beyond Linux kernel versions and commits. The issue is a resource-lifetime bug in pnv_php during nested bridge removal. Avoid assuming broader impact without confirming driver use and architecture-specific relevance in the target environment.
Mitigation direction
Update to a kernel containing the referenced stable fixes or your distribution’s backport.
Review Debian LTS and vendor advisories for packaged kernel updates.
Prioritize hosts using PCIe hotplug or pnv_php-managed hardware.
If patching is delayed, avoid nonessential PCIe hot-unplug operations on suspected affected systems.
Schedule maintenance windows for kernel updates on availability-sensitive servers.
Validation and detection
Inventory Linux kernel versions against affected stable lines and vendor advisories.
Confirm whether the pnv_php PCI hotplug driver is built, loaded, or relevant.
Verify the running kernel includes one of the referenced upstream stable commits or distro backport.
Check system logs for kernel panics or MSI warnings during PCIe hotplug events.
Validate hotplug behavior only in a lab or approved maintenance window.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38624 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
1ADP providers
10Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Aug 22, 2025, 16:00 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.