CVE-2026-99311
Description
A flaw was found in the Linux kernel's Universal Disk Format (UDF) file system. A local user capable of mounting or accessing a crafted file system image can cause a denial of service (DoS) through a system crash. When processing a corrupted symbolic link with an unexpected extent type, an internal block mapping function returns an improper status code. The kernel mistakenly treats this return code as a valid memory pointer, resulting in an invalid memory access that crashes the system.
Statement
This vulnerability is rated as having a Moderate impact because mounting an arbitrary filesystem requires elevated privileges such as CAP_SYS_ADMIN or physical access to attach removable media. In environments where unprivileged users cannot mount external storage, an attacker cannot independently trigger the issue. While processing a malformed UDF volume can crash the host, the flaw only causes a denial of service and does not compromise system confidentiality or integrity.
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 | 4.4 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | High | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Other
Technical Impact: Varies by Context
When the product accesses the resource using an incompatible type, this could trigger logical errors because the resource does not have expected properties.
Availability,Integrity,Confidentiality
Technical Impact: Read Memory; Modify Memory; Execute Unauthorized Code or Commands; DoS: Crash, Exit, or Restart
If a memory buffer is accessed using an incompatible type, and the allocated buffer is smaller than the type that the code is attempting to access, then an attacker could read or write memory outside the bounds of the buffer, leading to a crash or possibly code execution.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.