Skip to main content
VulnerabilityPublished

CVE-2026-99600: Linux kernel · udf: fix preallocation discarding before an empty allocation extent

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99600· High

Not known to be exploited · fixed in f7d6f3fed104ca7e48a9ed081c2047300d3f96fc : patch Linux kernel soon.

Data as of 20 Nov 2026, 07:34 UTC

Severity
High

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in f7d6f3fed104ca7e48a9ed081c2047300d3f96fc, 6.2, 6.1 +9

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=4.9.337 <4.10
  • >=4.14.303 <4.15
  • >=4.19.270 <4.20
  • >=5.4.229 <5.5
  • >=5.10.161 <5.11
  • >=5.15.85 <5.16
  • >=6.0.15 <6.1
  • >=6.1.1 <6.2
Fixed in
  • f7d6f3fed104ca7e48a9ed081c2047300d3f96fc
  • 6.2
  • 6.1
  • 5.16
  • 5.11
  • 5.5
  • 4ef0ffc5da8d2966d8f4bd0b6dc88a6fab2e891c
  • 4.20
  • 4.15
  • 4.10
  • 0efa27a0d8b8f4b75eed80728d2c331c6104c308
  • 0c52750caaaccee8b0e929450fe6538ec4985722
LinuxLinuxAffected
  • =6.2
Fixed in–

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.

References

Community reviews

Loading reviews…