Skip to content
Noroxi
CVE-2026-97948· NVD / CVE Program· CNA Linux

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

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

—No exploit Fix available
Published
Sep 25, 2026
Updated
Oct 3, 2026
EPSS
0.2% · 7th percentile
CWE
—
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • d42bbd8f30ac38b1ce54715bf08ec3dac18d6b25, 19d5036e7ad766cf212aebec23b9f1d7924a62bc, 6.17affected
    • 502f08831a9afb72dc98a56ae6504da43e93b250 and later · before 3833dfae0680b6b16e2469fbc90aa48376311cd8affected · git
    • f56e004b781719d8fdf6c9619b15caf2579bc1f2 and later · before 24524fca27da674668941440e8e05cdfec0b0222affected · git
    • 59c6d3d81d42bf543c90597b4f38c53d6874c5a1 and later · before a58531181363219fa5de2b53d5d7274dcdfca98baffected · git
    • a426e8a6ae161f51888585b065db0f8f93ab2e16 and later · before 460fab22b65138531082910702f74b048b25237baffected · git
    • d2c60a8a387e9fcc28447ef36c03f8e49fd052a6 and later · before 102e3dc5ab5ba052e294819e83384166b242c1ecaffected · git
    • 1010b4c012b0d78dfb9d3132b49aa2ef024a07a7 and later · before 2920af33d097ca335e492b346af70b72986ad6dcaffected · git
    • 1010b4c012b0d78dfb9d3132b49aa2ef024a07a7 and later · before 85d8eaefc052cf3e5ae2c7bafeda2db68b8898b4affected · git
    • 1010b4c012b0d78dfb9d3132b49aa2ef024a07a7 and later · before c5e68706527968282e49de205cc2b935823cb88aaffected · git
    • 5.10.241 and later · before 5.10.271affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxall versions—
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.7-17.2.7-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan
  • CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler
    40Plan
  • CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index
    40Plan
  • CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux102e3dc5ab5ba052e294819e83384166b242c1ecVendor (CNA)
Linux Linux24524fca27da674668941440e8e05cdfec0b0222Vendor (CNA)
Linux Linux2920af33d097ca335e492b346af70b72986ad6dcVendor (CNA)
Linux Linux3833dfae0680b6b16e2469fbc90aa48376311cd8Vendor (CNA)
Linux Linux460fab22b65138531082910702f74b048b25237bVendor (CNA)
Linux Linux5.10.271Vendor (CNA)
Linux Linux5.15.222Vendor (CNA)
Linux Linux6.1.189Vendor (CNA)
Linux Linux6.12.111Vendor (CNA)
Linux Linux6.16Vendor (CNA)
Linux Linux6.17Vendor (CNA)
Linux Linux6.6.158Vendor (CNA)
Linux Linux85d8eaefc052cf3e5ae2c7bafeda2db68b8898b4Vendor (CNA)
Linux Linuxa58531181363219fa5de2b53d5d7274dcdfca98bVendor (CNA)
Linux Linuxc5e68706527968282e49de205cc2b935823cb88aVendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records