CVE-2026-99717

Description

A flaw was found in the Linux kernel's PMBus q54sj108a2 hardware monitoring driver. When debug filesystem directory creation fails during device initialization, the driver fails to validate the returned pointer and creates debug files in the root directory instead of the device hierarchy. Because these files are not properly cleaned up when the device is disconnected, they remain orphaned in the filesystem. A local user accessing these orphaned entries can trigger a use-after-free condition, resulting in a system crash and Denial of Service (DoS).

Statement

This vulnerability is evaluated with a Moderate severity impact because triggering the flaw requires local privileged access alongside specialized hardware and uncommon failure conditions. On typical Red Hat Enterprise Linux deployments, access to the debugfs filesystem is restricted to the root user by default, preventing unprivileged actors from accessing orphaned debugfs nodes. Additionally, the affected PMBus driver is only relevant when Delta Q54SJ108A2 power supply devices are attached, meaning standard enterprise systems without this hardware are not exposed to the condition.

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 Score4.1N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredHighN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

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

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.

Frequently Asked Questions

Want to get errata notifications? Sign up here.