Skip to main content
VulnerabilityPublished

CVE-2026-99602: Linux kernel · udf: don't let the extent type hide an exhausted free-space table extent

Source GCVE Database

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

Not known to be exploited · fixed in da582d84fcf5f2f0c1d7760e1a899ca7cedb80fc : 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 da582d84fcf5f2f0c1d7760e1a899ca7cedb80fc, c4f8f503f2038269ffe9bca218bea65bbece9998, a40b887f4b67cf969c23e19c28b650d6b5e8afeb +1

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 Linux kernel to da582d84fcf5f2f0c1d7760e1a899ca7cedb80fc, c4f8f503f2038269ffe9bca218bea65bbece9998, a40b887f4b67cf969c23e19c28b650d6b5e8afeb or 78885b05188d3df733a9697d67bfcbb6d8330f76.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < da582d84fcf5f2f0c1d7760e1a899ca7cedb80fc
Fixed in
  • da582d84fcf5f2f0c1d7760e1a899ca7cedb80fc
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < c4f8f503f2038269ffe9bca218bea65bbece9998
Fixed in
  • c4f8f503f2038269ffe9bca218bea65bbece9998
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < a40b887f4b67cf969c23e19c28b650d6b5e8afeb
Fixed in
  • a40b887f4b67cf969c23e19c28b650d6b5e8afeb
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 78885b05188d3df733a9697d67bfcbb6d8330f76
Fixed in
  • 78885b05188d3df733a9697d67bfcbb6d8330f76
LinuxLinuxAffected
  • =2.6.12
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: udf: don't let the extent type hide an exhausted free-space table extent udf_table_new_block() takes the first block of the free-space table extent closest to the goal. It keeps that extent's type and length together in goal_elen, subtracts one block, and deletes the extent only if goal_elen then reaches zero. UDF 2.60 section 2.3.7.1 requires the free-space extents of an Unallocated Space Entry to be of type 1 (allocated but not recorded), and mkudffs writes them that way. For such an extent the type bits keep goal_elen non-zero, so taking its last block leaves a type-1 extent of length zero behind, starting at the block after the extent, which is in use. The next allocation that picks this empty extent returns that in-use block. Subtracting a block from 0x40000000 then borrows from the type bits, and the extent becomes type 0 with a length of 2^30 - blocksize: about a gigabyte of "free" space overlapping live metadata, the other table extents and whatever lies behind the partition. From then on blocks are handed out twice, or past the end of the partition. Extents that udf_table_free_blocks() adds are type 0, where the check works, so only tables written by mkudffs or by another implementation are affected. Nothing more than filling such a filesystem is needed: on a fresh 1 MiB "mkudffs --space=unalloctable" image, creating empty files until the partition is full writes file entries over the reserve volume descriptor sequence and the backup anchor, and df then reports a negative amount of used space. On syzbot's images the same double allocation is what the two reports below trip over. In the first, ftruncate() extends a new file with enough hole extents to need a chain of allocation extent descriptors; one AED is placed on another inode's file entry, and a later one is placed on the block of the AED currently being filled, which udf_setup_indirect_aext() zeroes, so __udf_add_aext() finds lengthAllocDescs out of step with its cursor. In the second, an AED is placed past the end of the device, sb_getblk() fails, and the error path of udf_do_extend_file() calls udf_truncate_extents() on an extent list that no longer covers i_size. Keep the type separately from the length, as udf_table_prealloc_blocks() already does.

References

Community reviews

Loading reviews…