CVE-2026-99569

Description

A flaw was found in the Linux kernel's F2FS (Flash-Friendly File System) implementation. When extended attributes (xattrs) shrink to fit directly within inline storage and the file is synchronized without a checkpoint, the roll-forward crash recovery process fails to release the obsolete extended attribute node. A local user could trigger this condition to cause file system corruption, resource leaks, or the unintended restoration of previously deleted file attributes after recovery.

Statement

This vulnerability is rated as Low impact for Red Hat Enterprise Linux because exploitation requires local access, specific timing around system crashes, and the use of the F2FS file system, which is not enabled by default in standard enterprise deployments. The flaw occurs during roll-forward crash recovery when extended file attributes are reduced to fit inline storage, potentially leaving behind orphaned attribute metadata or causing previously cleared attributes to persist. Given the high complexity of reproducing the crash recovery sequence and the absence of remote attack vectors, the overall risk to supported systems is minimal.

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 Score3.6N/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 ImpactLowN/AN/A

Vector

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

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Resource Consumption (Other); DoS: Resource Consumption (Memory); DoS: Resource Consumption (CPU)

An attacker that can influence the allocation of resources that are not properly released could deplete the available resource pool and prevent all other processes from accessing the same type of resource. Frequently-affected resources include memory, CPU, disk space, power or battery, etc.

Frequently Asked Questions

Want to get errata notifications? Sign up here.