Skip to main content

Linux EUVDEUVD-2026-86802

| CVE-2026-97948
2026-09-25 Linux GHSA-wgj5-j7wg-2jm2
View
Monitor Track and reassess. Why: No CVSS yet + weak signal (CWE or non-zero EPSS).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisCVE.org

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 VersionsENISA

Linux 1010b4c012b0d78dfb9d3132b49aa2ef024a07a7 <c5e68706527968282e49de205cc2b935823cb88a
Linux 59c6d3d81d42bf543c90597b4f38c53d6874c5a1
Linux 6.12.42 <6.12.111
Linux 19d5036e7ad766cf212aebec23b9f1d7924a62bc
Linux 1010b4c012b0d78dfb9d3132b49aa2ef024a07a7 <85d8eaefc052cf3e5ae2c7bafeda2db68b8898b4
Linux patch: 7.3-rc3
Linux 5.10.241 <5.11
Linux patch: 0
Linux 1010b4c012b0d78dfb9d3132b49aa2ef024a07a7 <2920af33d097ca335e492b346af70b72986ad6dc
Linux 5.15.190 <5.16
Linux 502f08831a9afb72dc98a56ae6504da43e93b250
Linux 6.15.10 <6.16
Linux f56e004b781719d8fdf6c9619b15caf2579bc1f2
Linux d2c60a8a387e9fcc28447ef36c03f8e49fd052a6 <102e3dc5ab5ba052e294819e83384166b242c1ec
Linux 6.16.1 <6.17
Linux patch: 6.12.111
Linux 6.6.102 <6.7
Linux patch: 7.2.7
Linux d42bbd8f30ac38b1ce54715bf08ec3dac18d6b25
Linux 6.17
Linux patch: 6.18.53
Linux a426e8a6ae161f51888585b065db0f8f93ab2e16
Linux 6.1.148 <6.2

Affected Packages

euvd linux fix: 5.11, 5.16, 6.2, 6.7, 6.12.111, 6.16, 6.17

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Lifecycle Timeline

2
Patch available
Sep 25, 2026 - 11:02 EUVD
CVE Published
Sep 25, 2026 - 10:22 cve.org
UNKNOWN (no severity yet)

Threat Intelligence Overview

EPSS Score
0.2%
Top 95% exploitable
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity Not scored yet
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
No CVSS yet + weak signal (CWE or non-zero EPSS)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy