Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-38624PCI: pnv_php: Clean up allocated IRQs on unplug

Description

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]

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 15 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38624, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 360aebd85a4c946764f6301d68de2a817fad5159 – < 8c1ad4af160691e157d688ad9619ced2df556aac
    • affected 360aebd85a4c946764f6301d68de2a817fad5159 – < 912e200240b6f9758f0b126e64a61c9227f4ad37
    • affected 360aebd85a4c946764f6301d68de2a817fad5159 – < 398170b7fd0e0db2f8096df5206c75e5ff41415a
    • affected 360aebd85a4c946764f6301d68de2a817fad5159 – < 32173edf3fe2d447e14e5e3b299387c6f9602a88
    • affected 360aebd85a4c946764f6301d68de2a817fad5159 – < 28aa3cfce12487614219e7667ec84424e1f43227
    • affected 360aebd85a4c946764f6301d68de2a817fad5159 – < 1773c19fa55e944cdd2634e2d9e552f87f2d38d5
    • affected 360aebd85a4c946764f6301d68de2a817fad5159 – < bbd302c4b79df10197ffa7270ca3aa572eeca33c
    • affected 360aebd85a4c946764f6301d68de2a817fad5159 – < 4668619092554e1b95c9a5ac2941ca47ba6d548a
  • Linux · Linux

    • affected 4.9
    • unaffected < 4.9
    • unaffected 5.10.241 – ≤ 5.10.*
    • unaffected 5.15.190 – ≤ 5.15.*
    • unaffected 6.1.148 – ≤ 6.1.*
    • unaffected 6.6.102 – ≤ 6.6.*
    • unaffected 6.12.42 – ≤ 6.12.*
    • unaffected 6.15.10 – ≤ 6.15.*
    • unaffected 6.16.1 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38624 badge
[![CVE-2025-38624](https://cveledger.app/badge/CVE-2025-38624.svg)](https://cveledger.app/cve/CVE-2025-38624)

Record last updated .