CVE-2025-38623: Linux kernel · PCI: pnv_php: Fix surprise plug detection and recovery
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in a2a2a6fc2469524caa713036297c542746d148dc : update Linux kernel when convenient.
Data as of 5 Nov 2026, 23:23 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-05.
- Patch
- Available – fixed in a2a2a6fc2469524caa713036297c542746d148dc, 473999ba937eac9776be791deed7c84a21d7880b, 78d20b8c13075eae3d884c21db7a09a6bbdda5b2 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 22 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 5 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: PCI: pnv_php: Fix surprise plug detection and recovery The existing PowerNV hotplug code did not handle surprise plug events correctly, leading to a complete failure of the hotplug system after device removal and a required reboot to detect new devices. This comes down to two issues: 1) When a device is surprise removed, often the bridge upstream port will cause a PE freeze on the PHB. If this freeze is not cleared, the MSI interrupts from the bridge hotplug notification logic will not be received by the kernel, stalling all plug events on all slots associated with the PE. 2) When a device is removed from a slot, regardless of surprise or programmatic removal, the associated PHB/PE ls left frozen. If this freeze is not cleared via a fundamental reset, skiboot is unable to clear the freeze and cannot retrain / rescan the slot. This also requires a reboot to clear the freeze and redetect the device in the slot. Issue the appropriate unfreeze and rescan commands on hotplug events, and don't oops on hotplug if pci_bus_to_OF_node() returns NULL. [bhelgaas: tidy comments]
References
- git.kernel.org/stable/c/6e7b5f922901585b8f11e0d6cda12bda5c59fc8a (opens in a new tab)
- git.kernel.org/stable/c/2ec8ec57bb8ebde3e2a015eff80e5d66e6634fe3 (opens in a new tab)
- git.kernel.org/stable/c/473999ba937eac9776be791deed7c84a21d7880b (opens in a new tab)
- git.kernel.org/stable/c/6e7b24c71e530a6c1d656e73d8a30ee081656844 (opens in a new tab)
- git.kernel.org/stable/c/48c6935a34981bb56f35be0774ec1f30c6e386f8 (opens in a new tab)
- git.kernel.org/stable/c/1d2f63680c5719a5da92639e981c6c9a87fcee08 (opens in a new tab)
- git.kernel.org/stable/c/78d20b8c13075eae3d884c21db7a09a6bbdda5b2 (opens in a new tab)
- git.kernel.org/stable/c/a2a2a6fc2469524caa713036297c542746d148dc (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html (opens in a new tab)