---
id: CVE-2026-97948
title: |-
  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 …
summary: |-
  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 …
severity: medium
cvss: 5.5
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'
cwe:
  - CWE-764
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 502f08831a9afb72dc98a56ae6504da43e93b250 <
    3833dfae0680b6b16e2469fbc90aa48376311cd8
  - >-
    Linux >= f56e004b781719d8fdf6c9619b15caf2579bc1f2 <
    24524fca27da674668941440e8e05cdfec0b0222
  - >-
    Linux >= 59c6d3d81d42bf543c90597b4f38c53d6874c5a1 <
    a58531181363219fa5de2b53d5d7274dcdfca98b
  - >-
    Linux >= a426e8a6ae161f51888585b065db0f8f93ab2e16 <
    460fab22b65138531082910702f74b048b25237b
  - >-
    Linux >= d2c60a8a387e9fcc28447ef36c03f8e49fd052a6 <
    102e3dc5ab5ba052e294819e83384166b242c1ec
  - >-
    Linux >= 1010b4c012b0d78dfb9d3132b49aa2ef024a07a7 <
    2920af33d097ca335e492b346af70b72986ad6dc
  - >-
    Linux >= 1010b4c012b0d78dfb9d3132b49aa2ef024a07a7 <
    85d8eaefc052cf3e5ae2c7bafeda2db68b8898b4
  - >-
    Linux >= 1010b4c012b0d78dfb9d3132b49aa2ef024a07a7 <
    c5e68706527968282e49de205cc2b935823cb88a
  - Linux d42bbd8f30ac38b1ce54715bf08ec3dac18d6b25
  - Linux 19d5036e7ad766cf212aebec23b9f1d7924a62bc
  - Linux >= 5.10.241 < 5.10.271
  - Linux >= 5.15.190 < 5.15.222
  - Linux >= 6.1.148 < 6.1.189
  - Linux >= 6.6.102 < 6.6.158
  - Linux >= 6.12.42 < 6.12.111
  - Linux >= 6.15.10 < 6.16
  - Linux >= 6.16.1 < 6.17
  - Linux 6.17
published: '2026-09-25'
updated: '2026-10-03'
sourceUpdated: '2026-10-03T11:18:19.963'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-97948'
references:
  - url: 'https://git.kernel.org/stable/c/102e3dc5ab5ba052e294819e83384166b242c1ec'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/24524fca27da674668941440e8e05cdfec0b0222'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/2920af33d097ca335e492b346af70b72986ad6dc'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/3833dfae0680b6b16e2469fbc90aa48376311cd8'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/460fab22b65138531082910702f74b048b25237b'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/85d8eaefc052cf3e5ae2c7bafeda2db68b8898b4'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/a58531181363219fa5de2b53d5d7274dcdfca98b'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/c5e68706527968282e49de205cc2b935823cb88a'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: >-
      https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97948.json
  - url: 'https://access.redhat.com/security/cve/CVE-2026-97948'
  - url: 'https://bugzilla.redhat.com/show_bug.cgi?id=2541132'
  - url: 'https://www.cve.org/CVERecord?id=CVE-2026-97948'
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2026-97948'
  - url: >-
      https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2026/CVE-2026-97948.mbox
tags:
  - nvd
  - cve.org
  - csaf
  - vex
  - red-hat
epss: 0.00176
epssPercentile: 0.07121
cvssSource: vendor
ingestedAt: '2026-09-25T11:06:38.879Z'
---

## Overview

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).

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

## Vendor advisories

- **Red Hat VEX** · Low · affected: Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 9, Red Hat OpenShift Container Platform 4 · no fix planned: Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 9, Red Hat OpenShift Container Platform 4 · updated 2026-10-17 · [vex](https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-97948.json)