CVE-2026-99602

Description

A flaw was found in the Universal Disk Format (UDF) file system implementation in the Linux kernel. When allocating blocks from a free-space table, the kernel fails to separate the extent type from its length, preventing exhausted extents from being deleted. A local user can exploit this flaw by writing to a UDF file system until space is exhausted, causing storage blocks to be allocated multiple times or past partition boundaries. This issue can lead to file system corruption and a system crash, resulting in a denial of service (DoS).

Statement

This vulnerability is rated as Moderate severity rather than Important because successful exploitation requires local user write access to a mounted, writable UDF filesystem, limiting the attack surface in standard enterprise environments. UDF is primarily utilized for optical media and removable storage, which are rarely mounted with write permissions on typical Red Hat Enterprise Linux server deployments. An unprivileged local attacker with permission to write to an affected mounted volume could induce filesystem corruption, leading to localized data integrity issues or a denial of service.

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 Score6.1N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactLowN/AN/A
Availability ImpactHighN/AN/A

Vector

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

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Instability

This weakness will generally lead to undefined behavior and therefore crashes. In the case of overflows involving loop index variables, the likelihood of infinite loops is also high.

Integrity

Technical Impact: Modify Memory

If the value in question is important to data (as opposed to flow), simple data corruption has occurred. Also, if the wrap around results in other conditions such as buffer overflows, further memory corruption may occur.

Confidentiality,Availability,Access Control

Technical Impact: Execute Unauthorized Code or Commands; Bypass Protection Mechanism

This weakness can sometimes trigger buffer overflows which can be used to execute arbitrary code. This is usually outside the scope of a program's implicit security policy.

Frequently Asked Questions

Want to get errata notifications? Sign up here.