CVE-2026-45904

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

powerpc/eeh: fix recursive pci_lock_rescan_remove locking in EEH event handling

The recent commit 1010b4c012b0 ("powerpc/eeh: Make EEH driver device hotplug safe") restructured the EEH driver to improve synchronization with the PCI hotplug layer.

However, it inadvertently moved pci_lock_rescan_remove() outside its intended scope in eeh_handle_normal_event(), leading to broken PCI error reporting and improper EEH event triggering. Specifically, eeh_handle_normal_event() acquired pci_lock_rescan_remove() before calling eeh_pe_bus_get(), but eeh_pe_bus_get() itself attempts to acquire the same lock internally, causing nested locking and disrupting normal EEH event handling paths.

This patch adds a boolean parameter do_lock to _eeh_pe_bus_get(), with two public wrappers: eeh_pe_bus_get() with locking enabled. eeh_pe_bus_get_nolock() that skips locking.

Callers that already hold pci_lock_rescan_remove() now use eeh_pe_bus_get_nolock() to avoid recursive lock acquisition.

Additionally, pci_lock_rescan_remove() calls are restored to the correct position—after eeh_pe_bus_get() and immediately before iterating affected PEs and devices. This ensures EEH-triggered PCI removes occur under proper bus rescan locking without recursive lock contention.

The eeh_pe_loc_get() function has been split into two functions: eeh_pe_loc_get(struct eeh_pe *pe) which retrieves the loc for given PE. eeh_pe_loc_get_bus(struct pci_bus *bus) which retrieves the location code for given bus.

This resolves lockdep warnings such as:

[ 84.964298] [ T928] ============================================ [ 84.964304] [ T928] WARNING: possible recursive locking detected [ 84.964311] [ T928] 6.18.0-rc3 #51 Not tainted [ 84.964315] [ T928] -------------------------------------------- [ 84.964320] [ T928] eehd/928 is trying to acquire lock: [ 84.964324] [ T928] c000000003b29d58 (pci_rescan_remove_lock){+.+.}-{3:3}, at: pci_lock_rescan_remove+0x28/0x40 [ 84.964342] [ T928] but task is already holding lock: [ 84.964347] [ T928] c000000003b29d58 (pci_rescan_remove_lock){+.+.}-{3:3}, at: pci_lock_rescan_remove+0x28/0x40 [ 84.964357] [ T928] other info that might help us debug this: [ 84.964363] [ T928] Possible unsafe locking scenario:

[ 84.964367] [ T928] CPU0 [ 84.964370] [ T928] ---- [ 84.964373] [ T928] lock(pci_rescan_remove_lock); [ 84.964378] [ T928] lock(pci_rescan_remove_lock); [ 84.964383] [ T928] * DEADLOCK *

[ 84.964388] [ T928] May be due to missing lock nesting notation

[ 84.964393] [ T928] 1 lock held by eehd/928: [ 84.964397] [ T928] #0: c000000003b29d58 (pci_rescan_remove_lock){+.+.}-{3:3}, at: pci_lock_rescan_remove+0x28/0x40 [ 84.964408] [ T928] stack backtrace: [ 84.964414] [ T928] CPU: 2 UID: 0 PID: 928 Comm: eehd Not tainted 6.18.0-rc3 #51 VOLUNTARY [ 84.964417] [ T928] Hardware name: IBM,9080-HEX POWER10 (architected) 0x800200 0xf000006 of:IBM,FW1060.00 (NH1060_022) hv:phyp pSeries [ 84.964419] [ T928] Call Trace: [ 84.964420] [ T928] [c0000011a7157990] [c000000001705de4] dump_stack_lvl+0xc8/0x130 (unreliable) [ 84.964424] [ T928] [c0000011a71579d0] [c0000000002f66e0] print_deadlock_bug+0x430/0x440 [ 84.964428] [ T928] [c0000011a7157a70] [c0000000002fd0c0] __lock_acquire+0x1530/0x2d80 [ 84.964431] [ T928] [c0000011a7157ba0] [c0000000002fea54] lock_acquire+0x144/0x410 [ 84.964433] [ T928] [c0000011a7157cb0] [c0000011a7157cb0] __mutex_lock+0xf4/0x1050 [ 84.964436] [ T928] [c0000011a7157e00] [c000000000de21d8] pci_lock_rescan_remove+0x28/0x40 [ 84.964439] [ T928] [c0000011a7157e20] [c00000000004ed98] eeh_pe_bus_get+0x48/0xc0 [ 84.964442] [ T928] [c0000011a7157e50] [c00000 ---truncated---

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 24, 2026

Advisory Details (8)

Auto-updated Jun 24, 2026
No patch confirmed yet.
generic

powerpc/eeh: fix recursive pci_lock_rescan_remove locking in EEH event handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f8b16d5764ee1e78c1ef333017ad383ffe76fcdc
generic

powerpc/eeh: fix recursive pci_lock_rescan_remove locking in EEH event handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f49faa4a64f8ac0e38983e606075b25dfcfc9ad4
generic

powerpc/eeh: fix recursive pci_lock_rescan_remove locking in EEH event handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b85ee287bfe52c6b2d9b41758b5e0d08679d5b39
generic

powerpc/eeh: fix recursive pci_lock_rescan_remove locking in EEH event handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/89810e2d80281d42f855fac813786758ee16e323
generic

powerpc/eeh: fix recursive pci_lock_rescan_remove locking in EEH event handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/87a1f93986aa1500b85aeff16b0b71c29ea116ea
generic

powerpc/eeh: fix recursive pci_lock_rescan_remove locking in EEH event handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/815a8d2feb5615ae7f0b5befd206af0b0160614c
generic

powerpc/eeh: fix recursive pci_lock_rescan_remove locking in EEH event handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/788dd28fd49610d6047cbb15dbf1186afffdfbaf
generic

powerpc/eeh: fix recursive pci_lock_rescan_remove locking in EEH event handling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6e6561231c6cfc32c5631aeecc0928ff2b14265c

Vendor Advisories for CVE-2026-45904(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(25)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-09-14ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-09-14ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-09-14ubuntu
ubuntulinux-tools-aws-edge (5.15.0.1112.119~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-09-14ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-09-14ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-09-14ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-09-14ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1057.58~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-09-14ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-09-14ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-09-14ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-09-14ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-09-14ubuntu
linuxKernel @ 5.10.252—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (103 versions)6.18.14-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(24)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 10× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 204 total refreshes for this CVE.

  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-14 09:07 UTCEG score recompute
  3. 2026-09-14 09:07 UTCVendor advisory
  4. 2026-09-14 09:06 UTCGHSA enrichment
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-13 04:09 UTCOSV refresh
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 09:37 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 13:54 UTCEPSS rescore
  17. 2026-08-30 19:17 UTCEPSS rescore
  18. 2026-08-30 01:22 UTCEPSS rescore
  19. 2026-08-28 21:41 UTCEPSS rescore
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-26 14:46 UTCEPSS rescore
  22. 2026-08-25 13:49 UTCEPSS rescore
  23. 2026-08-25 05:44 UTCEG score recompute
  24. 2026-08-25 05:44 UTCVendor advisory
  25. 2026-08-25 05:44 UTCGHSA enrichment
Show 75 more
  1. 2026-08-23 15:32 UTCEG score recompute
  2. 2026-08-23 15:32 UTCVendor advisory
  3. 2026-08-23 15:32 UTCGHSA enrichment
  4. 2026-08-21 23:49 UTCEPSS rescore
  5. 2026-08-21 20:53 UTCEG score recompute
  6. 2026-08-21 20:53 UTCVendor advisory
  7. 2026-08-21 20:52 UTCGHSA enrichment
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-20 17:41 UTCEG score recompute
  10. 2026-08-20 17:41 UTCVendor advisory
  11. 2026-08-20 17:41 UTCGHSA enrichment
  12. 2026-08-19 17:04 UTCEPSS rescore
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 09:21 UTCEG score recompute
  16. 2026-08-17 09:21 UTCVendor advisory
  17. 2026-08-17 09:21 UTCGHSA enrichment
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 02:54 UTCEG score recompute
  20. 2026-08-16 02:54 UTCVendor advisory
  21. 2026-08-16 02:54 UTCGHSA enrichment
  22. 2026-08-16 02:14 UTCEPSS rescore
  23. 2026-08-15 01:30 UTCEPSS rescore
  24. 2026-08-14 05:58 UTCEG score recompute
  25. 2026-08-14 05:58 UTCVendor advisory
  26. 2026-08-14 05:58 UTCGHSA enrichment
  27. 2026-08-13 22:00 UTCEPSS rescore
  28. 2026-08-13 04:50 UTCEG score recompute
  29. 2026-08-13 04:50 UTCVendor advisory
  30. 2026-08-13 04:50 UTCGHSA enrichment
  31. 2026-08-12 13:51 UTCEPSS rescore
  32. 2026-08-12 03:43 UTCEG score recompute
  33. 2026-08-12 03:43 UTCVendor advisory
  34. 2026-08-12 03:43 UTCGHSA enrichment
  35. 2026-08-11 02:35 UTCEG score recompute
  36. 2026-08-11 02:35 UTCVendor advisory
  37. 2026-08-11 02:35 UTCGHSA enrichment
  38. 2026-08-11 00:00 UTCEPSS rescore
  39. 2026-08-10 01:27 UTCEG score recompute
  40. 2026-08-10 01:27 UTCVendor advisory
  41. 2026-08-10 01:27 UTCGHSA enrichment
  42. 2026-08-09 13:46 UTCEPSS rescore
  43. 2026-08-09 00:20 UTCEG score recompute
  44. 2026-08-09 00:20 UTCVendor advisory
  45. 2026-08-09 00:20 UTCGHSA enrichment
  46. 2026-08-08 16:37 UTCEPSS rescore
  47. 2026-08-07 23:11 UTCVendor advisory
  48. 2026-08-07 23:11 UTCGHSA enrichment
  49. 2026-08-06 22:04 UTCEG score recompute
  50. 2026-08-06 22:04 UTCVendor advisory
  51. 2026-08-06 22:04 UTCGHSA enrichment
  52. 2026-08-06 13:47 UTCEPSS rescore
  53. 2026-08-05 20:55 UTCEG score recompute
  54. 2026-08-05 20:55 UTCVendor advisory
  55. 2026-08-05 20:55 UTCGHSA enrichment
  56. 2026-08-05 19:17 UTCEPSS rescore
  57. 2026-08-04 15:10 UTCEPSS rescore
  58. 2026-08-04 10:39 UTCEPSS rescore
  59. 2026-08-03 18:44 UTCEG score recompute
  60. 2026-08-03 18:44 UTCVendor advisory
  61. 2026-08-03 18:44 UTCGHSA enrichment
  62. 2026-08-03 10:36 UTCEPSS rescore
  63. 2026-08-02 16:52 UTCEG score recompute
  64. 2026-08-02 16:52 UTCVendor advisory
  65. 2026-08-02 16:52 UTCGHSA enrichment
  66. 2026-08-02 02:27 UTCEPSS rescore
  67. 2026-08-01 15:43 UTCEG score recompute
  68. 2026-08-01 15:43 UTCVendor advisory
  69. 2026-08-01 15:43 UTCGHSA enrichment
  70. 2026-08-01 04:16 UTCEPSS rescore
  71. 2026-07-31 08:03 UTCEG score recompute
  72. 2026-07-31 08:03 UTCVendor advisory
  73. 2026-07-31 08:03 UTCGHSA enrichment
  74. 2026-07-30 16:28 UTCEPSS rescore
  75. 2026-07-30 01:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-45904?
CVE-2026-45904 is a medium vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: powerpc/eeh: fix recursive pcilockrescan_remove locking in EEH event handling The recent commit 1010b4c012b0 ("powerpc/eeh: Make EEH driver device hotplug safe") restructured the EEH driver to improve synchronization with the PCI…
When was CVE-2026-45904 disclosed?
CVE-2026-45904 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45904 actively exploited?
CVE-2026-45904 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.4% of all scored CVEs.
What is the CVSS score of CVE-2026-45904?
CVE-2026-45904 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-45904?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45904, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45904

Explore →

Is Your Infrastructure Affected by CVE-2026-45904?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs