CVE-2026-97948

powerpc/eeh: Fix recursive locking on devices without EEH sensitive driver

N/A
Published: September 25, 2026 at 10:22 AM UTC
Updated: October 19, 2026 at 10:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: powerpc/eeh: Fix recursive locking on devices without EEH sensitive driver The commit 1010b4c012b0 ("powerpc/eeh: Make EEH driver device hotplug safe") refactored the EEH code such that the pci_rescan_remove_lock is held at the beginning of eeh_handle_normal_event() and the eeh_reset_device() is called with that lock being held. Looks like the commit missed to remove the existing lock/unlock inside eeh_rmv_device() which is no longer necessary. This is causing the eehd to hang on the lock which it actually holds when that code path is taken. [<0>] 0xc00000011c78f870 [<0>] __switch_to+0xfc/0x1a0 [<0>] pci_lock_rescan_remove+0x30/0x44 [<0>] eeh_rmv_device+0x290/0x2e0 [<0>] eeh_pe_dev_traverse+0x80/0x130 [<0>] eeh_reset_device+0xcc/0x23c [<0>] eeh_handle_normal_event+0x830/0xa80 [<0>] eeh_event_handler+0xf8/0x190 [<0>] kthread+0x194/0x1b0 [<0>] start_kernel_thread+0x14/0x18 The issue is seen for cases where the errors are detected on the PHB directly AND|OR for devices where the driver error_detected() returns PCI_ERS_RESULT_NEED_RESET, and driver being not EEH sensitive(i.e no error handlers like slot_reset(), resume() etc defined).

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1010b4c012b0d78dfb9d3132b49aa2ef024a07a719d5036e7ad766cf212aebec23b9f1d7924a62bc5.10.2415.15.190502f08831a9afb72dc98a56ae6504da43e93b25059c6d3d81d42bf543c90597b4f38c53d6874c5a16.1.1486.12.426.15.106.16.16.176.6.102a426e8a6ae161f51888585b065db0f8f93ab2e16d2c60a8a387e9fcc28447ef36c03f8e49fd052a6d42bbd8f30ac38b1ce54715bf08ec3dac18d6b25f56e004b781719d8fdf6c9619b15caf2579bc1f2
Vendor states this is fixed in 102e3dc5ab5ba052e294819e83384166b242c1ec (fixed)
Vendor states this is fixed in 24524fca27da674668941440e8e05cdfec0b0222 (fixed)
Vendor states this is fixed in 2920af33d097ca335e492b346af70b72986ad6dc (fixed)
Vendor states this is fixed in 3833dfae0680b6b16e2469fbc90aa48376311cd8 (fixed)
Vendor states this is fixed in 460fab22b65138531082910702f74b048b25237b (fixed)
Vendor states this is fixed in 85d8eaefc052cf3e5ae2c7bafeda2db68b8898b4 (fixed)
Vendor states this is fixed in a58531181363219fa5de2b53d5d7274dcdfca98b (fixed)
Vendor states this is fixed in c5e68706527968282e49de205cc2b935823cb88a (fixed)
Vendor states this is fixed in 5.10.271 (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Affected range stops below 6.16, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.17 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2.7 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc3 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card