CVE-2026-99600

udf: fix preallocation discarding before an empty allocation extent

State
Published
Severity
Not scored
Published
Nov 20, 2026
Updated
Nov 20, 2026
Reserved
Sep 25, 2026

Read the record on cve.org

Description

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

udf: fix preallocation discarding before an empty allocation extent

udf_discard_prealloc() finds the last extent of a file by peeking at the next one with udf_next_aext() and stopping when that returns 0. The peek reads into eloc and elen, and the code then uses them as the last extent. But when udf_next_aext() returns 0 they hold no defined value: if the extent list ends in a continuation descriptor that leads to an empty allocation extent, they describe that continuation, i.e. the block of the empty allocation extent, one block long.

The kernel creates such lists itself: when udf_delete_aext() removes the only descriptor of the last allocation extent in a list, it leaves that allocation extent empty and the continuation to it in place.

If the last extent is a preallocation, udf_discard_prealloc() deletes it with udf_delete_aext(), which finds the following allocation extent empty, so it also removes the continuation and frees that allocation extent's block. udf_discard_prealloc() then frees eloc and elen: that block a second time, instead of the preallocated blocks. On a space bitmap the preallocated blocks leak and the free block count drifts. On an unallocated space table the second free adds a second free extent for the same block, which is later handed out twice: fsx as run by generic/091 and generic/263 ends up with two parts of its test file in one block and reads back bad data.

Peek into separate variables, so that eloc and elen keep the last extent that udf_next_aext() returned with 1.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • cfe4c1b25dd6d2f056afc00b7c98bcb3dd0b1fc3 to before 4ef0ffc5da8d2966d8f4bd0b6dc88a6fab2e891cAffected
  • cfe4c1b25dd6d2f056afc00b7c98bcb3dd0b1fc3 to before f7d6f3fed104ca7e48a9ed081c2047300d3f96fcAffected
  • cfe4c1b25dd6d2f056afc00b7c98bcb3dd0b1fc3 to before 0efa27a0d8b8f4b75eed80728d2c331c6104c308Affected
  • cfe4c1b25dd6d2f056afc00b7c98bcb3dd0b1fc3 to before 0c52750caaaccee8b0e929450fe6538ec4985722Affected
  • c8b6fa4511a7900db9fb0353b630d4d2ed1ba99cAffected
  • 7665857f88557c372da35534165721156756f77fAffected
  • 72f651c96c8aadf087fd782d551bf7db648a8c2eAffected
  • 4d835efd561dfb9bf5409f11f4ecd428d5d29226Affected
  • 1a075f4a549481ce6e8518d8379f193ccec6b746Affected
  • 63dbbd8f1499b0a161e701a04aa50148d60bd1f7Affected
  • ae56d9a017724f130cf1a263dd82a78d2a6e3852Affected
  • 12a88f572d6d94b5c0b72e2d1782cc2e96ac06cfAffected
  • 4.9.337 to before 4.10Affected
  • 4.14.303 to before 4.15Affected
  • 4.19.270 to before 4.20Affected
  • 5.4.229 to before 5.5Affected
  • 5.10.161 to before 5.11Affected
  • 5.15.85 to before 5.16Affected
  • 6.0.15 to before 6.1Affected
  • 6.1.1 to before 6.2Affected
LinuxLinux
  • 6.2Affected
  • before 6.2Not affected
  • 6.12.118 through 6.12.*Not affected
  • 6.18.64 through 6.18.*Not affected
  • 7.3.5 through 7.3.*Not affected
  • 7.4-rc2 and laterNot affected

References

Every record here comes from the CVE Program's CVE List. © 1999-2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.

© 2026 NVIDIA, the NVIDIA logo, and NVIDIA Inception are trademarks and/or registered trademarks of NVIDIA Corporation in the U.S. and other countries.