CVE-2026-99601: udf: check the unallocated space table when it is loaded
In the Linux kernel, the following vulnerability has been resolved:
udf: check the unallocated space table when it is loaded
udftablenewblock() hands out the first block of the extent closest to its goal and trusts that the extent covers at least one whole block inside the partition. Nothing checks that. A zero-length extent makes it return the block the extent points at, which need not be free, and the subtraction of one block then underflows the length into the type bits, turning the entry into a bogus continuation. An extent running past the end of the partition makes it return blocks behind the partition.
Such tables are not only found on crafted images: until the previous commit, udftablenewblock() itself left zero-length extents behind in tables written by mkudffs, and then converted them into extents running past the partition.
Check every extent once when the table is loaded, and refuse read-write access if one is empty, is not a whole number of blocks, or does not lie inside the partition, in the same way as for other allocation information the kernel cannot use. Check first that the table is an Unallocated Space Entry at all: the walk starts at the offset of the allocation descriptors in one, and for a file entry that offset lies before the inode's in-memory copy of the descriptors. Treat a chain of allocation extent descriptors that leads back to itself the same way: the walk would otherwise return the same extents forever, and the mount would never finish. Let a fatal signal interrupt the walk and fail the mount.
Refusing read-write access to an empty extent is deliberate. It shows that an old kernel took the last block but left the entry behind. If consumed again, the entry returns an in-use block and turns into a huge bogus extent. Refusing the table before that happens avoids this second allocation; the filesystem can still be mounted read-only. The check cannot detect every overlap that may already exist in a damaged table.
This patch should be backported together with the previous one: that patch stops creating new empty extents, and this one rejects existing ones before they are consumed again.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Compensating control
When loading a UDF unallocated-space table, validate each extent once and refuse read-write access if an extent is empty, is not a whole number of blocks, or runs past the partition. Detect allocation-extent descriptor chains that loop back to themselves and fail the mount; the filesystem may still be mounted read-only.
Frequently Asked Questions
When is a system exposed to this issue?
The issue applies when the Linux kernel loads a UDF unallocated space table containing invalid extents, including zero-length extents, extents that are not a whole number of blocks, or extents outside the partition. Such malformed tables can exist on crafted UDF images and, before the referenced prior fix, could also be produced by mkudffs-written tables.
What must an attacker control to trigger the vulnerable behavior?
An attacker would need to provide or cause the system to use a UDF filesystem image with a malformed unallocated space table. The described invalid entries can cause allocation to select blocks that are not free or lie beyond the partition.
How does the resolved behavior affect mounting affected UDF filesystems?
The fix validates each extent when the unallocated space table is loaded. If an extent is empty, not block-aligned, or outside the partition, the kernel refuses read-write access rather than using the invalid allocation information.
How can administrators identify filesystems affected by the new validation?
A UDF filesystem is affected by the validation if it is denied read-write access because its unallocated space table contains an empty extent, a non-whole-block extent, or an extent outside the partition. The description specifically notes that older mkudffs-written tables may contain these conditions.