CVE-2026-99394 in Linuxinfo

Summary

by MITRE • 11/19/2026

In the Linux kernel, the following vulnerability has been resolved:

xfs: complain loudly when dirtree checker finds broken links

LOLLM observed that the directory tree walk code bails out if it finds broken parent pointers along the way. However, it flattens the return code to zero, which means that we can end up in the repair code having not completed the scan. We should never proceed with a repair in this state, so let's mark the scrub incomplete and exit.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 11/19/2026

The Linux kernel’s XFS filesystem driver contains a logic flaw within its directory tree verification mechanism that allows for potentially unsafe repair operations on corrupted file systems. This vulnerability centers on how the xfs_scrub utility handles broken parent pointers during a traversal of the directory hierarchy. When the dirtree checker encounters links where the parent pointer does not correctly reference an existing inode, it detects a structural inconsistency in the filesystem metadata. While the code initially recognizes this error and halts further processing along that specific branch to prevent invalid operations, it subsequently normalizes or flattens the return status code to zero before passing control back to the higher-level repair logic. This normalization effectively masks the detection of corruption from the overarching scrubbing process.

From a technical perspective, this behavior represents an improper handling of error states where critical failure conditions are silently ignored rather than propagated up the call stack. The flaw lies in the assumption that reaching the end of a directory tree walk implies success, even if intermediate steps encountered fatal structural errors. By resetting the return code to zero, the system signals to the repair engine that no issues were found or that all detected issues have been successfully resolved. This misrepresentation of status prevents the scrubber from marking the filesystem state as incomplete or requiring manual intervention for severe corruption cases. The issue is particularly dangerous because it can lead to a false sense of security regarding the integrity of the XFS volume, allowing automated repair scripts to proceed with modifications on a file system that still contains broken links and inconsistent metadata structures.

The operational impact of this vulnerability is significant for data integrity and system reliability. If an administrator or automated tool relies on the scrubber’s output to determine whether a filesystem is healthy enough for online repairs, they may inadvertently trigger repair procedures on a corrupted volume. Repairing a file system with unresolved broken parent pointers can exacerbate existing corruption, potentially leading to further metadata degradation, loss of directory structure coherence, or in severe cases, complete unmountability of the partition. This undermines the primary purpose of filesystem scrubbing, which is to detect and safely rectify inconsistencies before they cause data loss. The flaw essentially allows a partially corrupted state to be treated as clean, bypassing critical safety checks designed to protect against cascading failures during maintenance operations.

This vulnerability aligns with CWE-252, Check for Unusual or Exceptional Conditions, where the software fails to properly check for error conditions that indicate corruption or invalid states. It also relates to CWE-754: Improper Check for Unusual or Exceptional Conditions in a critical path of execution. In terms of attack vectors and defensive mapping, this issue can be contextualized within MITRE ATT&CK techniques related to Defense Evasion, specifically T1070.006: Indicator Removal on Host using File Deletion or Modification, although here the modification is unintentional due to software logic rather than malicious intent. The flaw allows a corrupted state to evade detection by standard health checks, effectively hiding evidence of filesystem damage from automated monitoring and repair tools.

To mitigate this risk, it is essential that system administrators ensure their Linux kernels are updated with patches that correct the return code handling in the xfs dirtree checker logic. The fix involves ensuring that any detected broken parent pointers result in a non-zero status being returned to the scrubbing framework, thereby forcing an incomplete state flag rather than a success signal. Until such updates are applied, administrators should exercise extreme caution when running online repair tools on XFS volumes and consider performing offline checks or manual verification of directory structures if corruption is suspected. Regular monitoring of kernel update channels for fixes related to xfs_scrub and filesystem integrity utilities is recommended to maintain the reliability of storage infrastructure dependent on these mechanisms.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/19/2026

Moderation

accepted

CPE

ready

EPSS

0.00224

KEV

no

Activities

very low

Sources

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!