CVE-2026-99404 in Linuxinfo

Summary

by MITRE • 11/19/2026

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

xfs: check fork type against dabtree block magic number

LOLLM complains that we fail to flag dabtree blocks that should never be associated with the file fork -- data forks can't point to xattr leaves, and attr forks can't point to dirent blocks. Add the missing checks.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/19/2026

The Linux kernel's XFS filesystem implementation contains a logic flaw related to the validation of extent fork types against directory attribute tree block magic numbers. This vulnerability arises from an insufficient check during the processing of file system metadata, specifically when handling data forks and extended attribute (xattr) leaves or directory entries. In normal operation, XFS uses different fork structures within inode records to store various types of file attributes, such as standard data extents for regular files, extended attributes stored in B-trees, and directory entry blocks for directories. The kernel previously failed to strictly enforce the correlation between the type of fork being accessed and the expected magic number found in the associated disk block header. This oversight allows scenarios where a data fork might incorrectly reference an xattr leaf structure or an attribute fork might point to dirent blocks intended for directory structures, violating fundamental filesystem integrity constraints.

From a technical perspective, this issue represents a failure in input validation at the metadata level. The XFS codebase relies on magic numbers embedded within block headers to identify the type of data stored in those blocks, ensuring that subsequent parsing logic applies the correct interpretation rules. When these checks are absent or incomplete, as highlighted by static analysis tools like LOLLM (Linux Object Lifecycle and Logic Manager), the kernel may proceed with operations assuming a specific structure exists when another is present. This mismatch can lead to memory corruption, incorrect data retrieval, or filesystem inconsistency because the parsing routines will interpret bit patterns according to one schema while the underlying storage adheres to another. The absence of these boundary checks creates an avenue for exploiting malformed on-disk structures that could be crafted by a local user with write access to the affected file system volume.

The operational impact of this vulnerability is primarily centered around filesystem stability and data integrity rather than direct remote code execution or privilege escalation, although severe corruption can lead to denial-of-service conditions through kernel panics or hangs. An attacker who gains the ability to manipulate low-level block structures on an XFS partition could potentially trigger these invalid associations during file system operations such as opening files, reading attributes, or traversing directories. While direct exploitation requires significant control over disk blocks and typically implies local access with elevated privileges, the resulting instability can disrupt services relying on persistent storage. Furthermore, repeated occurrences of this corruption may lead to silent data loss if the filesystem continues to operate in a degraded state without immediate detection by standard integrity checks.

Mitigation strategies involve applying kernel patches that introduce rigorous validation logic before processing fork-related metadata. Developers must ensure that every access to an extent block verifies that its magic number corresponds exactly to the expected type for the current fork context, thereby preventing cross-type confusion between data forks and attribute structures. System administrators should prioritize updating their Linux kernels to versions where this specific XFS fix is included. Additionally, running regular filesystem checks using tools like xfs_repair can help detect and correct any existing inconsistencies that may have arisen from prior exposure to the flaw. Aligning with industry standards such as CWE-20 Improper Input Validation highlights the necessity of strict type checking in system-level software to maintain robust security postures against malformed data attacks. This vulnerability also relates to ATT&CK techniques involving local privilege escalation or defense evasion through filesystem manipulation, underscoring the importance of maintaining up-to-date kernel components to close these low-level logic gaps.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/19/2026

Moderation

accepted

CPE

ready

EPSS

0.00215

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!