CVE-2026-99574

Description

A flaw was found in the Linux kernel's Flash-Friendly File System (f2fs). A local user capable of mounting a specially crafted file system image could exploit this flaw to trigger an out-of-bounds memory read, leading to information disclosure or a Denial of Service (DoS) through a system crash. This issue occurs because the f2fs driver does not properly validate checkpoint bitmap sizes against the allocated memory buffer, allowing adjacent kernel memory to be read and written back to disk.

Statement

This vulnerability is rated as Moderate severity for Red Hat enterprise products because exploitation requires local privileges or physical access to mount a maliciously crafted file system, limiting the immediate blast radius. Under default configurations, unprivileged users cannot mount arbitrary storage volumes, substantially restricting exposure. While an attacker capable of supplying a corrupted filesystem structure can cause an out-of-bounds read leading to kernel memory disclosure or a kernel panic, remote unauthenticated exploitation is not possible.

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 Score5.1N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredHighN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityLowN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

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

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.

Confidentiality

Technical Impact: Bypass Protection Mechanism

Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.

Other

Technical Impact: Varies by Context

The read operation could produce other undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.