PT-2026-98612 · Linux · Linux

CVE-2026-97948

·

Published

2026-09-25

·

Updated

2026-09-25

None

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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).
Found an issue in the description? Have something to add? Feel free to write us 👾

Related Identifiers

CVE-2026-97948

Affected Products

Linux