CVE-2026-99602 (GCVE-0-2026-99602)
Vulnerability from cvelistv5 – Published: 2026-11-20 05:49 – Updated: 2026-11-20 05:49| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < a40b887f4b67cf969c23e19c28b650d6b5e8afeb
(git)
Affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < 78885b05188d3df733a9697d67bfcbb6d8330f76 (git) Affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < c4f8f503f2038269ffe9bca218bea65bbece9998 (git) Affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < da582d84fcf5f2f0c1d7760e1a899ca7cedb80fc (git) |
guessed | |
| Linux | Linux |
Affected:
2.6.12
Unaffected: 0 , < 2.6.12 (semver) Unaffected: 6.12.118 , ≤ 6.12.* (semver) Unaffected: 6.18.64 , ≤ 6.18.* (semver) Unaffected: 7.3.5 , ≤ 7.3.* (semver) Unaffected: 7.4-rc2 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/udf/balloc.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "a40b887f4b67cf969c23e19c28b650d6b5e8afeb",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "78885b05188d3df733a9697d67bfcbb6d8330f76",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "c4f8f503f2038269ffe9bca218bea65bbece9998",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "da582d84fcf5f2f0c1d7760e1a899ca7cedb80fc",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/udf/balloc.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "2.6.12"
},
{
"lessThan": "2.6.12",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.118",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.64",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc2",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.118",
"versionStartIncluding": "2.6.12",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.64",
"versionStartIncluding": "2.6.12",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3.5",
"versionStartIncluding": "2.6.12",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.4-rc2",
"versionStartIncluding": "2.6.12",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nudf: don\u0027t let the extent type hide an exhausted free-space table extent\n\nudf_table_new_block() takes the first block of the free-space table\nextent closest to the goal. It keeps that extent\u0027s type and length\ntogether in goal_elen, subtracts one block, and deletes the extent only\nif goal_elen then reaches zero. UDF 2.60 section 2.3.7.1 requires the\nfree-space extents of an Unallocated Space Entry to be of type 1\n(allocated but not recorded), and mkudffs writes them that way. For\nsuch an extent the type bits keep goal_elen non-zero, so taking its last\nblock leaves a type-1 extent of length zero behind, starting at the\nblock after the extent, which is in use.\n\nThe next allocation that picks this empty extent returns that in-use\nblock. Subtracting a block from 0x40000000 then borrows from the type\nbits, and the extent becomes type 0 with a length of 2^30 - blocksize:\nabout a gigabyte of \"free\" space overlapping live metadata, the other\ntable extents and whatever lies behind the partition. From then on\nblocks are handed out twice, or past the end of the partition.\n\nExtents that udf_table_free_blocks() adds are type 0, where the check\nworks, so only tables written by mkudffs or by another implementation\nare affected. Nothing more than filling such a filesystem is needed:\non a fresh 1 MiB \"mkudffs --space=unalloctable\" image, creating empty\nfiles until the partition is full writes file entries over the reserve\nvolume descriptor sequence and the backup anchor, and df then reports a\nnegative amount of used space.\n\nOn syzbot\u0027s images the same double allocation is what the two reports\nbelow trip over. In the first, ftruncate() extends a new file with\nenough hole extents to need a chain of allocation extent descriptors;\none AED is placed on another inode\u0027s file entry, and a later one is\nplaced on the block of the AED currently being filled, which\nudf_setup_indirect_aext() zeroes, so __udf_add_aext() finds\nlengthAllocDescs out of step with its cursor. In the second, an AED\nis placed past the end of the device, sb_getblk() fails, and the error\npath of udf_do_extend_file() calls udf_truncate_extents() on an extent\nlist that no longer covers i_size.\n\nKeep the type separately from the length, as udf_table_prealloc_blocks()\nalready does."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T05:49:27.678Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/a40b887f4b67cf969c23e19c28b650d6b5e8afeb"
},
{
"url": "https://git.kernel.org/stable/c/78885b05188d3df733a9697d67bfcbb6d8330f76"
},
{
"url": "https://git.kernel.org/stable/c/c4f8f503f2038269ffe9bca218bea65bbece9998"
},
{
"url": "https://git.kernel.org/stable/c/da582d84fcf5f2f0c1d7760e1a899ca7cedb80fc"
}
],
"title": "udf: don\u0027t let the extent type hide an exhausted free-space table extent",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99602",
"datePublished": "2026-11-20T05:49:27.678Z",
"dateReserved": "2026-09-25T10:25:14.424Z",
"dateUpdated": "2026-11-20T05:49:27.678Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-99602",
"date": "2026-11-20",
"epss": "0.00168",
"percentile": "0.0628"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/udf/balloc.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "a40b887f4b67cf969c23e19c28b650d6b5e8afeb",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "78885b05188d3df733a9697d67bfcbb6d8330f76",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "c4f8f503f2038269ffe9bca218bea65bbece9998",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "da582d84fcf5f2f0c1d7760e1a899ca7cedb80fc",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/udf/balloc.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "2.6.12"
},
{
"lessThan": "2.6.12",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.118",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.64",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.3.*",
"status": "unaffected",
"version": "7.3.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.4-rc2",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nudf: don\u0027t let the extent type hide an exhausted free-space table extent\n\nudf_table_new_block() takes the first block of the free-space table\nextent closest to the goal. It keeps that extent\u0027s type and length\ntogether in goal_elen, subtracts one block, and deletes the extent only\nif goal_elen then reaches zero. UDF 2.60 section 2.3.7.1 requires the\nfree-space extents of an Unallocated Space Entry to be of type 1\n(allocated but not recorded), and mkudffs writes them that way. For\nsuch an extent the type bits keep goal_elen non-zero, so taking its last\nblock leaves a type-1 extent of length zero behind, starting at the\nblock after the extent, which is in use.\n\nThe next allocation that picks this empty extent returns that in-use\nblock. Subtracting a block from 0x40000000 then borrows from the type\nbits, and the extent becomes type 0 with a length of 2^30 - blocksize:\nabout a gigabyte of \"free\" space overlapping live metadata, the other\ntable extents and whatever lies behind the partition. From then on\nblocks are handed out twice, or past the end of the partition.\n\nExtents that udf_table_free_blocks() adds are type 0, where the check\nworks, so only tables written by mkudffs or by another implementation\nare affected. Nothing more than filling such a filesystem is needed:\non a fresh 1 MiB \"mkudffs --space=unalloctable\" image, creating empty\nfiles until the partition is full writes file entries over the reserve\nvolume descriptor sequence and the backup anchor, and df then reports a\nnegative amount of used space.\n\nOn syzbot\u0027s images the same double allocation is what the two reports\nbelow trip over. In the first, ftruncate() extends a new file with\nenough hole extents to need a chain of allocation extent descriptors;\none AED is placed on another inode\u0027s file entry, and a later one is\nplaced on the block of the AED currently being filled, which\nudf_setup_indirect_aext() zeroes, so __udf_add_aext() finds\nlengthAllocDescs out of step with its cursor. In the second, an AED\nis placed past the end of the device, sb_getblk() fails, and the error\npath of udf_do_extend_file() calls udf_truncate_extents() on an extent\nlist that no longer covers i_size.\n\nKeep the type separately from the length, as udf_table_prealloc_blocks()\nalready does."
}
],
"id": "CVE-2026-99602",
"lastModified": "2026-11-20T06:17:52.237",
"metrics": {},
"published": "2026-11-20T06:17:52.237",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/78885b05188d3df733a9697d67bfcbb6d8330f76"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/a40b887f4b67cf969c23e19c28b650d6b5e8afeb"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/c4f8f503f2038269ffe9bca218bea65bbece9998"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/da582d84fcf5f2f0c1d7760e1a899ca7cedb80fc"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-20T11:58:23+00:00",
"cve": "CVE-2026-99602",
"id": "CVE-2026-99602",
"initial_release_date": "2026-11-20T05:49:27.678000+00:00",
"product_status:known_affected": "204",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: kernel: udf: File system corruption via improper free-space extent handling",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99602.json",
"version": "3"
}
}
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.