CVE-2026-99242
Description
A flaw was found in the Linux kernel's NTFS file system implementation. A race condition between file space preallocation and memory-mapped file operations allows newly allocated storage blocks to be accessed before they are cleared. A local user can exploit this vulnerability by reading memory-mapped files during concurrent space allocation, leading to information disclosure of stale or uninitialized disk data.
Statement
This vulnerability is rated as Moderate impact for Red Hat products because exploitation requires existing local user access and permissions to write to an NTFS-formatted filesystem. Red Hat Enterprise Linux does not deploy NTFS as a primary filesystem, generally restricting its presence to optional removable media or secondary partitions. The flaw allows the disclosure of stale or uninitialized storage blocks during concurrent allocation operations, but does not provide privileges to execute arbitrary code or compromise system 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 Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | High | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | None | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Understanding the Weakness (CWE)
Integrity,Availability
Technical Impact: Modify Application Data; DoS: Instability; DoS: Crash, Exit, or Restart
When a resource is not properly locked, an attacker could modify the resource while it is being operated on by the product. This might violate the product's assumption that the resource will not change, potentially leading to unexpected behaviors.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
