CVE-2026-99599: Linux kernel · udf: don't use eloc after the end of the unallocated space table
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 94401199df90e1c2a50c6e4b73618ac5a4ba83ba : update Linux kernel when convenient.
Data as of 20 Nov 2026, 06:04 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 94401199df90e1c2a50c6e4b73618ac5a4ba83ba, 812d49a09ce0a8fcc784349d6a95e975a4af51cf, 9ecd3d7ed7d7a57ee6af27dc22be0b3fdc9526f7 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade Linux kernel to 94401199df90e1c2a50c6e4b73618ac5a4ba83ba, 812d49a09ce0a8fcc784349d6a95e975a4af51cf, 9ecd3d7ed7d7a57ee6af27dc22be0b3fdc9526f7 or 0ceb311c0f7af4f4b38fc1066178b84a60d61a05.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
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.
References
- git.kernel.org/stable/c/0ceb311c0f7af4f4b38fc1066178b84a60d61a05 (opens in a new tab)
- git.kernel.org/stable/c/812d49a09ce0a8fcc784349d6a95e975a4af51cf (opens in a new tab)
- git.kernel.org/stable/c/9ecd3d7ed7d7a57ee6af27dc22be0b3fdc9526f7 (opens in a new tab)
- git.kernel.org/stable/c/94401199df90e1c2a50c6e4b73618ac5a4ba83ba (opens in a new tab)