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-38576powerpc/eeh: Make EEH driver device hotplug safe

Description

In the Linux kernel, the following vulnerability has been resolved: powerpc/eeh: Make EEH driver device hotplug safe Multiple race conditions existed between the PCIe hotplug driver and the EEH driver, leading to a variety of kernel oopses of the same general nature: <pcie device unplug> <eeh driver trigger> <hotplug removal trigger> <pcie tree reconfiguration> <eeh recovery next step> <oops in EEH driver bus iteration loop> A second class of oops is also seen when the underlying bus disappears during device recovery. Refactor the EEH module to be PCI rescan and remove safe. Also clean up a few minor formatting / readability issues.

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-38576, 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 1c2042c83aa7af10579b71a1fe5e22bbae69f08c – < 502f08831a9afb72dc98a56ae6504da43e93b250
    • affected 1c2042c83aa7af10579b71a1fe5e22bbae69f08c – < f56e004b781719d8fdf6c9619b15caf2579bc1f2
    • affected 1c2042c83aa7af10579b71a1fe5e22bbae69f08c – < 59c6d3d81d42bf543c90597b4f38c53d6874c5a1
    • affected 1c2042c83aa7af10579b71a1fe5e22bbae69f08c – < a426e8a6ae161f51888585b065db0f8f93ab2e16
    • affected 1c2042c83aa7af10579b71a1fe5e22bbae69f08c – < d2c60a8a387e9fcc28447ef36c03f8e49fd052a6
    • affected 1c2042c83aa7af10579b71a1fe5e22bbae69f08c – < d42bbd8f30ac38b1ce54715bf08ec3dac18d6b25
    • affected 1c2042c83aa7af10579b71a1fe5e22bbae69f08c – < 19d5036e7ad766cf212aebec23b9f1d7924a62bc
    • affected 1c2042c83aa7af10579b71a1fe5e22bbae69f08c – < 1010b4c012b0d78dfb9d3132b49aa2ef024a07a7
  • Linux · Linux

    • affected 3.14
    • unaffected < 3.14
    • 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-38576 badge
[![CVE-2025-38576](https://cveledger.app/badge/CVE-2025-38576.svg)](https://cveledger.app/cve/CVE-2025-38576)

Record last updated .