CVE-2026-99599

Description

A flaw was found in the Linux kernel's Universal Disk Format (UDF) file system, which can lead to data corruption. When traversing the unallocated space table, the system continues to process extent location values even after reaching the end of the table. A local user performing standard file system operations can trigger this issue, causing the kernel to reallocate storage blocks that are already in use or write invalid partition metadata to disk. This flaw primarily results in file system inconsistencies and data corruption.

Statement

This vulnerability is rated as Low severity because triggering the issue requires local access and the ability to perform write operations on an active UDF file system, a format typically reserved for optical media and rarely mounted read-write in enterprise server environments. Furthermore, the risk is confined to potential corruption within the mounted UDF volume rather than arbitrary code execution or system-wide compromise. Exploitation depends on encountering specific space-allocation boundary conditions during unallocated extent traversal.

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)

Confidentiality

Technical Impact: Read Memory; Read Application Data

When reusing a resource such as memory or a program variable, the original contents may not have been cleared before it is sent to an untrusted party.

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Instability

The uninitialized resource may contain values that cause program flow to change in ways that the programmer did not intend, possibly leading to a crash.

Other

Technical Impact: Unexpected State; Varies by Context

The consequences vary depending on the type of resource and how it is used within the product.

Frequently Asked Questions

Want to get errata notifications? Sign up here.