Bug 2573861 (CVE-2026-99311) - CVE-2026-99311 kernel: kernel: Denial of Service via corrupted UDF filesystem symlink
Summary: CVE-2026-99311 kernel: kernel: Denial of Service via corrupted UDF filesystem...
Keywords:
Status: NEW
Alias: CVE-2026-99311
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-16 21:44 UTC by OSIDB Bzimport
Modified: 2026-11-16 23:14 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-16 21:44:29 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.