UNKNOWNCVSS not yet scoredVulnerability

CVE-2026-99599

In the Linux kernel, the following vulnerability has been resolved: udf: don't use eloc after the end of the unallocated space table When udf_next_aext() 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. udf_table_prealloc_blocks() looks for a free extent starting at first_block and decides whether it found one by comparing eloc with first_block 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 first_block, the block is handed out as preallocation. Once udf_discard_prealloc() 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 udf_table_free_blocks() 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.

Properties

Last source
FIRST EPSS
Nvd fetched at
2026-11-22T12:30:49.958423+00:00
Epss score
0.00168
Cve id
CVE-2026-99599
First seen by Signal
2026-11-20T07:38:10+00:00
Name
CVE-2026-99599
Retrieved at
2026-11-22T12:32:29+00:00
Published at
2026-11-20T06:17:51.780
Last modified
2026-11-20T06:17:51.780
Epss percentile
0.06192

Related research

Explore deeper with Ninja Signal's threat intelligence graph

CVE-2026-99599 — Ninja Signal Threat Intelligence | Ninja Signal