Read the docs

Incorrect return value in Linux kernel UDF can crash symlink reads

Priority LOW 22Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
—
Confidentiality · integrity · availability
—
Fix status
Fixed

No CVSS vector from any source. Fix status from CNA.

Summary

The Linux kernel udf filesystem is affected from 6.6.59 before 6.7, from 6.11.6 before 6.12, and from 6.12. In udf_map_block(), the return value is not reset to 0 for extents other than recorded-allocated ones, so a corrupted UDF filesystem with such a symlink can crash the system when the link is read. An attacker who can create a corrupted UDF filesystem can trigger this crash.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

Description from the CNA

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.

Why it matters now

EPSS 0.00209 11th percentileScored 2026-11-16
Fix Fixed Linux (Linux): 6.7, 6.12, 6.12.117 +3

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
LinuxLinux6.6.59 to before 6.7; 6.11.6 to before 6.126.7, 6.12Patch availableCNA
LinuxLinux6.12 and later6.12.117, 6.18.61, 7.3.2, 7.4-rc1Patch availableCNA
  • Linux VendorLinux Affected 6.6.59 to before 6.7; 6.11.6 to before 6.12 Fixed in 6.7, 6.12 Patch available CNA
  • Linux VendorLinux Affected 6.12 and later Fixed in 6.12.117, 6.18.61, 7.3.2, 7.4-rc1 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*——Linux
  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* Versions — — ·Linux

Remediation

Upgrade the Linux kernel to 6.7, 6.12, 6.12.117, 6.18.61, 7.3.2 or 7.4-rc1, depending on the branch in use.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

  • Fix · CNA Linux (Linux) Fixed in 6.7, 6.12
  • Fix · CNA Linux (Linux) Fixed in 6.12.117, 6.18.61, 7.3.2, 7.4-rc1

Timeline

  1. 2026-11-16 Threatist record created from CVE-2026-99311
  2. 2026-11-16 Alias added: GHSA-6m96-2phx-3668

References

  • TI-2025-26358 Zero-length TLS records mishandled on rx_list in Linux kernel KEVCVSS 3.1CRITICAL 9.8
  • TI-2026-38352 Out-of-bounds write in Linux kernel ebtables SNAT ARP rewrite KEVCVSS 3.1HIGH 8.8
  • TI-2021-02452 Overlayfs flaw in Linux kernel lets attackers gain elevated privileges KEVCVSS 3.1HIGH 8.8
  • TI-2013-05264 Missing address checks in Linux kernel get_user and put_user on ARM KEVCVSS 3.1HIGH 8.8
  • TI-2022-00125 Heap overflow in Linux kernel lets local users escalate privileges KEVCVSS 3.1HIGH 8.4
  • TI-2013-01864 Wrong integer type in Linux kernel perf_swevent_init KEVCVSS 3.1HIGH 8.4
See all 21768 →

Sources