CVE-2026-45904

Description

A flaw was found in the Linux kernel's PowerPC Enhanced Error Handling (EEH) driver. This issue involves a recursive locking mechanism where the system attempts to acquire a Peripheral Component Interconnect (PCI) bus lock multiple times. This can lead to a system deadlock, causing unresponsiveness and a Denial of Service (DoS) for affected systems.

Statement

This vulnerability is rated as having a Low impact because it strictly affects IBM Power (PowerPC) systems during runtime PCI error recovery scenarios. Triggering the deadlock requires an active Enhanced Error Handling (EEH) event, which is generated by underlying hardware faults or device hotplug operations rather than arbitrary unprivileged user actions. Non-Power architectures are completely unaffected, substantially restricting the blast radius in typical enterprise deployments.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.55.5N/A
Attack VectorLocalLocalN/A
Attack ComplexityLowLowN/A
Privileges RequiredLowLowN/A
User InteractionNoneNoneN/A
ScopeUnchangedUnchangedN/A
ConfidentialityNoneNoneN/A
Integrity ImpactNoneNoneN/A
Availability ImpactHighHighN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

NVD: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Other); DoS: Crash, Exit, or Restart

Each thread of execution will "hang" and prevent tasks from completing. In some cases, CPU consumption may occur if a lock check occurs in a tight loop.

Frequently Asked Questions

Want to get errata notifications? Sign up here.