CVE-2026-99394

Description

A flaw was found in the XFS file system component of the Linux kernel. When the online directory tree checking mechanism encounters broken parent pointers, it aborts the scan but incorrectly reports success instead of marking the process as incomplete. A local attacker could leverage a corrupted file system to cause repair routines to execute prematurely with partial scan data, leading to file system metadata corruption and data integrity loss.

Statement

This vulnerability is rated as Moderate severity because initiating an online filesystem repair requires administrative privileges, which restricts unprivileged users from directly triggering the flaw. In typical Red Hat enterprise deployments, filesystem corruption can only occur if a privileged administrator or service invokes online metadata repair against an XFS volume already suffering from broken parent pointers. Because the issue does not permit remote access, privilege escalation, or confidentiality loss, the security impact remains constrained to filesystem integrity under specific administrative workflows.

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 Score6N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredHighN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactHighN/AN/A
Availability ImpactHighN/AN/A

Vector

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

Understanding the Weakness (CWE)

Integrity,Other

Technical Impact: Unexpected State; Alter Execution Logic

This weakness can lead to unpredictable behavior. If the function is used to make security-critical decisions or provide security-critical information, then the wrong status code can cause the product to assume that an action is safe or correct, even when it is not. This weakness could place the system in a state that could lead unexpected logic to be executed or other unintended behaviors.

Frequently Asked Questions

Want to get errata notifications? Sign up here.