CVE-2026-99600
What it is
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.
At a glance
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: not scored yet.
- Severity: not scored yet.
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Record status
- Received
Affected
- Linux < 4ef0ffc5da8d2966d8f4bd0b6dc88a6fab2e891c
- Linux < f7d6f3fed104ca7e48a9ed081c2047300d3f96fc
- Linux < 0efa27a0d8b8f4b75eed80728d2c331c6104c308
- Linux < 0c52750caaaccee8b0e929450fe6538ec4985722
- Linux c8b6fa4511a7900db9fb0353b630d4d2ed1ba99c
- Linux 7665857f88557c372da35534165721156756f77f
- Linux 72f651c96c8aadf087fd782d551bf7db648a8c2e
- Linux 4d835efd561dfb9bf5409f11f4ecd428d5d29226
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-99600.md and follow it. Check whether this project is affected by CVE-2026-99600. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.