CVE-2026-99602: Linux/kernel vulnerability

Published Nov 20, 2026

In the Linux kernel, the following vulnerability has been resolved:

udf: don't let the extent type hide an exhausted free-space table extent

udftablenewblock() takes the first block of the free-space table extent closest to the goal. It keeps that extent's type and length together in goalelen, subtracts one block, and deletes the extent only if goalelen then reaches zero. UDF 2.60 section 2.3.7.1 requires the free-space extents of an Unallocated Space Entry to be of type 1 (allocated but not recorded), and mkudffs writes them that way. For such an extent the type bits keep goalelen non-zero, so taking its last block leaves a type-1 extent of length zero behind, starting at the block after the extent, which is in use.

The next allocation that picks this empty extent returns that in-use block. Subtracting a block from 0x40000000 then borrows from the type bits, and the extent becomes type 0 with a length of 2^30 - blocksize: about a gigabyte of "free" space overlapping live metadata, the other table extents and whatever lies behind the partition. From then on blocks are handed out twice, or past the end of the partition.

Extents that udftablefreeblocks() adds are type 0, where the check works, so only tables written by mkudffs or by another implementation are affected. Nothing more than filling such a filesystem is needed: on a fresh 1 MiB "mkudffs --space=unalloctable" image, creating empty files until the partition is full writes file entries over the reserve volume descriptor sequence and the backup anchor, and df then reports a negative amount of used space.

On syzbot's images the same double allocation is what the two reports below trip over. In the first, ftruncate() extends a new file with enough hole extents to need a chain of allocation extent descriptors; one AED is placed on another inode's file entry, and a later one is placed on the block of the AED currently being filled, which udfsetupindirectaext() zeroes, so udfaddaext() finds lengthAllocDescs out of step with its cursor. In the second, an AED is placed past the end of the device, sbgetblk() fails, and the error path of udfdoextendfile() calls udftruncateextents() on an extent list that no longer covers isize.

Keep the type separately from the length, as udftablepreallocblocks() already does.

Affected Software

3 affected componentsFixes available
linux/kernel>=2.6.12<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5

Frequently Asked Questions

1

Which UDF filesystems are exposed to this allocation corruption?

The issue affects UDF free-space table extents of type 1, which UDF 2.60 requires for Unallocated Space Entries and which mkudffs writes. Extents later added by udf_table_free_blocks() are type 0 and are not described as triggering this specific type-bit behavior.

2

What must occur for the corruption to begin?

An allocation must consume the final block of a type-1 free-space table extent. Because the extent type bits keep the combined type-and-length value nonzero, the exhausted extent is retained and a subsequent allocation can return a block already in use.

3

What is the impact after an exhausted extent is reused?

The allocator can create a very large apparent free extent overlapping live metadata, other table extents, and potentially space beyond the partition. Blocks may then be allocated more than once or allocated past the end of the partition.

4

How can this be identified from filesystem behavior?

The described condition leaves a zero-length type-1 free-space extent beginning at the block immediately after the exhausted extent; that block is already in use. Subsequent allocation can turn this into an apparent free extent of roughly a gigabyte, depending on block size.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203