CVE-2026-99311

udf: fix return value for non-recorded-allocated extents in udf_map_block()

Published Nov 16, 2026 CVSS n/a EPSS n/a KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

udf: fix return value for non-recorded-allocated extents in udf_map_block()

When someone creates a corrupted UDF filesystem where symlink contains
other extent type than EXT_RECORDED_ALLOCATED, it can leads to a crash
like:

Oops: general protection fault
KASAN: maybe wild-memory-access
RIP: 0010:page_get_link (fs/namei.c:6503)
Call Trace:
vfs_readlink (fs/namei.c:6419)
do_readlinkat (fs/stat.c:583)
__x64_sys_readlink (fs/stat.c:605 fs/stat.c:602 fs/stat.c:602)

This is because in this case udf_map_block() fails to convert return
value of inode_bmap() from 1 to 0. Returned '1' propagates through
udf_bread() all the way up to __page_get_link() where it ends up being
treated as a folio pointer with obvious results.

Move the reset to 0 line outside the if, so udf_map_block() returns either
0 or -errno, even if the extent type is not EXT_RECORDED_ALLOCATED.

Analysis

AI-generated

Technical impact

The Linux kernel’s UDF filesystem handler incorrectly propagates a return value of 1 from inode_bmap() when processing non-recorded‑allocated extents in udf_map_block(). The function treats the value as a valid pointer, leading to a general protection fault and a kernel panic when a readlink operation touches the corrupted symlink. The fault can bring the system down, creating a local denial of service. The vulnerability does not directly lead to code execution, but it does compromise system availability.

Affected Systems

All Linux kernels incorporating the UDF implementation prior to the commit that moved the reset value outside the conditional block are affected. The patch is present in the mainline tree after commit 0d7f6c2b and is recommended for any distribution that uses the default kernel package. No specific version numbers were supplied, however any kernels built from source before the patch are vulnerable.

Risk and Exploitability

The bug carries a high severity because it can cause a kernel panic. An EPSS score is not available, and the vulnerability is not listed in CISA’s KEV catalog, indicating no known active exploitation campaigns as of the latest data. An attacker can exploit the code locally by mounting a crafted UDF image or, if the system exposes remote UDF mounts, remotely. The exploit requires the ability to create or mount a corrupted UDF filesystem, so the attack surface is bounded to environments that allow such operations.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the kernel to a version that incorporates the patch (commit 0d7f6c2b or later). For example, on a Debian‑based system run "apt update && apt install --only-upgrade linux-image-$(uname -r)" or use the equivalent command for your distribution.
  • If an immediate kernel upgrade is not feasible, avoid mounting UDF filesystems or refuse untrusted UDF volumes to reduce the attack surface.
  • Monitor for kernel panic events on systems handling UDF volumes and apply the patch as soon as it is available; consider disabling debug or crash‑logging mechanisms temporarily until the fix is deployed.

Generated by OpenCVE AI on November 16, 2026 at 11:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-843
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: udf: fix return value for non-recorded-allocated extents in udf_map_block() When someone creates a corrupted UDF filesystem where symlink contains other extent type than EXT_RECORDED_ALLOCATED, it can leads to a crash like: Oops: general protection fault KASAN: maybe wild-memory-access RIP: 0010:page_get_link (fs/namei.c:6503) Call Trace: vfs_readlink (fs/namei.c:6419) do_readlinkat (fs/stat.c:583) __x64_sys_readlink (fs/stat.c:605 fs/stat.c:602 fs/stat.c:602) This is because in this case udf_map_block() fails to convert return value of inode_bmap() from 1 to 0. Returned '1' propagates through udf_bread() all the way up to __page_get_link() where it ends up being treated as a folio pointer with obvious results. Move the reset to 0 line outside the if, so udf_map_block() returns either 0 or -errno, even if the extent type is not EXT_RECORDED_ALLOCATED.
Title udf: fix return value for non-recorded-allocated extents in udf_map_block()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-843

    Access of Resource Using Incompatible Type ('Type Confusion')

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Nov 16, 2026, 9:59 AM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Nov 16, 2026, 10:17 AM
Modified
Nov 16, 2026, 10:17 AM