CVE-2026-99599: udf: don't use eloc after the end of the unallocated space table

Published Nov 20, 2026
·
Updated

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

udf: don't use eloc after the end of the unallocated space table

When udfnextaext() returns 0, its eloc, elen and etype outputs hold no defined value. Two walks of the unallocated space table still use eloc after the walk has reached the end of the table.

udftablepreallocblocks() looks for a free extent starting at firstblock and decides whether it found one by comparing eloc with firstblock after the walk. If the table's list ends in a continuation descriptor that leads to an empty allocation extent, eloc is then the block of that allocation extent, which is in use, and if that is firstblock, the block is handed out as preallocation. Once udfdiscardprealloc() no longer frees the wrong block, this is what still makes fsx in generic/091 and generic/263 read back bad data on a table, in about one run in four. Only take the extent if the walk stopped at it.

When udftablefreeblocks() cannot merge the freed blocks into an existing extent, it appends a new one and sets only its block number, so the partition reference comes from whatever eloc held after the walk, and with long allocation descriptors it is written to disk. For a table without extents, eloc was never set. Take the partition reference from the freed blocks instead. Short allocation descriptors do not store the partition reference, which is why this half remains a latent long-descriptor fix rather than a reproduced failure.

Affected Software

7 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
debian/linux*
debian/linux*
debian/linux*
debian/linux<=6.1.176-1, <=6.1.192-2, <=6.12.107-1, <=6.12.117-1, <=7.3.4-1
7.3.5-1

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
  4. Upgrade

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

    Fixed in 7.3.5-1

Event History

Nov 20, 2026
CVE Published
via MITRE·05:49 AM
Data Sourced
via MITRE·05:49 AM
Description
Data Sourced
via OSV·05:49 AM
DescriptionAffected Software
Data Sourced
via NVD·06:17 AM
Description

Frequently Asked Questions

1

Which systems are exposed to this issue?

Linux kernel systems using UDF filesystems can be affected when the unallocated space table ends in a continuation descriptor that leads to an empty allocation extent. The affected paths walk that table while preallocating or freeing blocks.

2

What conditions trigger the incorrect block handling?

The problem occurs when the allocation-extent walk reaches the end of the table and returns no extent, leaving its output location undefined. In the preallocation path, the stale location can match the requested first block and cause a block that is already in use to be handed out.

3

What is the practical impact?

The incorrect preallocation can lead to bad data being read back, as observed in filesystem tests. When freed blocks cannot be merged into an existing extent, a newly appended extent may also inherit a partition reference from the stale location value.

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