CVE-2026-99607

Description

A flaw was found in the ext2 file system in the Linux kernel. When performing synchronous direct input/output (I/O) write operations that extend a file, the driver prematurely clears an internal metadata tracking flag. As a result, write operations can return successfully without the updated file size being committed to persistent storage. This issue could lead to data loss or metadata inconsistency if an unexpected system crash or power failure occurs before an explicit synchronization.

Statement

Red Hat rates this flaw as Low severity because exploitation is restricted to local authenticated users, requires non-default ext2 filesystem mounts, and only risks delayed metadata persistence during sudden power loss rather than privilege escalation or memory corruption. In standard Red Hat Enterprise Linux environments, ext2 is legacy and rarely deployed in production, where filesystems such as XFS are standard. Additionally, the issue is constrained to specific direct synchronous I/O operations on devices supporting Force Unit Access, causing no compromise of system confidentiality or availability.

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 Score2.5N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactLowN/AN/A
Availability ImpactNoneN/AN/A

Vector

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

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.