Skip to main content
VulnerabilityPublished

CVE-2026-99601: Linux kernel · udf: check the unallocated space table when it is loaded

Source GCVE Database

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

Not known to be exploited · fixed in e614c3e35a6699ed691b4d17e1ec4230e34aa3eb : 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 e614c3e35a6699ed691b4d17e1ec4230e34aa3eb, 88401035fbfcad7067793455326262ac30633586, 302eb1fa5be5e476a633d8ed0fd56ea5efa57374 +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 e614c3e35a6699ed691b4d17e1ec4230e34aa3eb, 88401035fbfcad7067793455326262ac30633586, 302eb1fa5be5e476a633d8ed0fd56ea5efa57374 or 9f3df19234d2c180b9a99b0d3c2472e8fade5043.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < e614c3e35a6699ed691b4d17e1ec4230e34aa3eb
Fixed in
  • e614c3e35a6699ed691b4d17e1ec4230e34aa3eb
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 88401035fbfcad7067793455326262ac30633586
Fixed in
  • 88401035fbfcad7067793455326262ac30633586
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 302eb1fa5be5e476a633d8ed0fd56ea5efa57374
Fixed in
  • 302eb1fa5be5e476a633d8ed0fd56ea5efa57374
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 9f3df19234d2c180b9a99b0d3c2472e8fade5043
Fixed in
  • 9f3df19234d2c180b9a99b0d3c2472e8fade5043
LinuxLinuxAffected
  • =2.6.12
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: udf: check the unallocated space table when it is loaded udf_table_new_block() hands out the first block of the extent closest to its goal and trusts that the extent covers at least one whole block inside the partition. Nothing checks that. A zero-length extent makes it return the block the extent points at, which need not be free, and the subtraction of one block then underflows the length into the type bits, turning the entry into a bogus continuation. An extent running past the end of the partition makes it return blocks behind the partition. Such tables are not only found on crafted images: until the previous commit, udf_table_new_block() itself left zero-length extents behind in tables written by mkudffs, and then converted them into extents running past the partition. Check every extent once when the table is loaded, and refuse read-write access if one is empty, is not a whole number of blocks, or does not lie inside the partition, in the same way as for other allocation information the kernel cannot use. Check first that the table is an Unallocated Space Entry at all: the walk starts at the offset of the allocation descriptors in one, and for a file entry that offset lies before the inode's in-memory copy of the descriptors. Treat a chain of allocation extent descriptors that leads back to itself the same way: the walk would otherwise return the same extents forever, and the mount would never finish. Let a fatal signal interrupt the walk and fail the mount. Refusing read-write access to an empty extent is deliberate. It shows that an old kernel took the last block but left the entry behind. If consumed again, the entry returns an in-use block and turns into a huge bogus extent. Refusing the table before that happens avoids this second allocation; the filesystem can still be mounted read-only. The check cannot detect every overlap that may already exist in a damaged table. This patch should be backported together with the previous one: that patch stops creating new empty extents, and this one rejects existing ones before they are consumed again.

References

Community reviews

Loading reviews…