CVE-2026-99602
udf: don't let the extent type hide an exhausted free-space table extent
No exploitation reported by the sources we read.
- Published2026-11-20
- Fixed in7.3.5 · 6.18.64 · 6.12.118
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2026-11-2005:49CVE publishedCNA
Versions per branch
OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.3 | ≥ 6.19.0, < 7.3.5 | 7.3.5 | OSV |
| 6.x | ≥ 6.13.0, < 6.18.64 | 6.18.64 | OSV |
| 6.12 | ≥ 2.6.12, < 6.12.118 | 6.12.118 | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA2 products
As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- Linuxother versions: not affected
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected- ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < a40b887f4b67cf969c23e19c28b650d6b5e8afebfixed in a40b887f4b67cf969c23e19c28b650d6b5e8afebgit
- ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 78885b05188d3df733a9697d67bfcbb6d8330f76fixed in 78885b05188d3df733a9697d67bfcbb6d8330f76git
- ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < c4f8f503f2038269ffe9bca218bea65bbece9998fixed in c4f8f503f2038269ffe9bca218bea65bbece9998git
- ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < da582d84fcf5f2f0c1d7760e1a899ca7cedb80fcfixed in da582d84fcf5f2f0c1d7760e1a899ca7cedb80fcgit
- Linuxother versions: affected
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected- = 2.6.12no fix stated
Not affected < 2.6.12 · ≥ 6.12.118, ≤ 6.12.* · ≥ 6.18.64, ≤ 6.18.* · ≥ 7.3.5, ≤ 7.3.* · ≥ 7.4-rc2
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE terms of useCVE recordupdated 2026-11-20
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- kernelAzure Linux:3all versions · no fixed version listed
- linuxDebian:14all versions · no fixed version listed
- linuxDebian:13all versions · fixed in 6.12.118-1
- linuxDebian:12all versions · no fixed version listed
- linux-ltsAlpaquita:streamfrom 6.18.62-r0 · fixed in 6.18.64-r0
- linux-ltsAlpaquita:25from 6.12.115-r0 · no fixed version listed
- linux-ltsAlpaquita:23from 6.1.191-r1 · no fixed version listed
Vendor advisories
kernel: kernel: udf: File system corruption via improper free-space extent handling
kernel.src as a component of Red Hat Enterprise Linux 10 · kernel as a component of Red Hat Enterprise Linux 6 · kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6 · +201 more
Fix
- Update Linux kernel to 7.3.5 · 6.18.64 · 6.12.118
- No fix available, says the vendor Red Hat Product Security CVE-2026-99602 · 190 productsFix deferred
- No fix planned, says the vendor Red Hat Product Security CVE-2026-99602 · 14 productsOut of support scope
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-11-22
- CNACVSS 3.17.12026-11-22
- FIRST EPSSEPSS score0.2 %2026-11-21
- OSVaffected packages—
- GitHub Advisoriesadvisory—
Identifiers
- AZL-115363same flawAzure Linux · MIT
- EUVD-2026-131052same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-f4rj-3f27-8x82same flawGitHub Advisory Database · CC-BY-4.0
- DSA-6652-1advisory covering several CVEsDebian · LicenseRef-unstated
Technical details
- CVSS v3 vector
- CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
- Published
- 2026-11-20
- Last modified
- 2026-11-22
- NVD status
- Received
- GitHub advisory
- GHSA-f4rj-3f27-8x82
Frequently asked questions
What is CVE-2026-99602?
Is CVE-2026-99602 actively exploited?
What is the CVSS score for CVE-2026-99602?
Running Linux kernel? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website checks · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-f4rj-3f27-8x82
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served
- Red Hat Product Security (CSAF and VEX) · CC-BY-4.0