CVE-2026-99601 (GCVE-0-2026-99601)
Vulnerability from cvelistv5 – Published: 2026-11-20 05:49 – Updated: 2026-11-20 05:49| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < 9f3df19234d2c180b9a99b0d3c2472e8fade5043
(git)
Affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < 88401035fbfcad7067793455326262ac30633586 (git) Affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < 302eb1fa5be5e476a633d8ed0fd56ea5efa57374 (git) Affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < e614c3e35a6699ed691b4d17e1ec4230e34aa3eb (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/super.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "9f3df19234d2c180b9a99b0d3c2472e8fade5043",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "88401035fbfcad7067793455326262ac30633586",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "302eb1fa5be5e476a633d8ed0fd56ea5efa57374",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "e614c3e35a6699ed691b4d17e1ec4230e34aa3eb",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/udf/super.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: check the unallocated space table when it is loaded\n\nudf_table_new_block() hands out the first block of the extent closest\nto its goal and trusts that the extent covers at least one whole block\ninside the partition. Nothing checks that. A zero-length extent makes\nit return the block the extent points at, which need not be free, and\nthe subtraction of one block then underflows the length into the type\nbits, turning the entry into a bogus continuation. An extent running\npast the end of the partition makes it return blocks behind the\npartition.\n\nSuch tables are not only found on crafted images: until the previous\ncommit, udf_table_new_block() itself left zero-length extents behind\nin tables written by mkudffs, and then converted them into extents\nrunning past the partition.\n\nCheck every extent once when the table is loaded, and refuse\nread-write access if one is empty, is not a whole number of blocks, or\ndoes not lie inside the partition, in the same way as for other\nallocation information the kernel cannot use. Check first that the\ntable is an Unallocated Space Entry at all: the walk starts at the\noffset of the allocation descriptors in one, and for a file entry that\noffset lies before the inode\u0027s in-memory copy of the descriptors.\nTreat a chain of allocation extent descriptors that leads back to\nitself the same way: the walk would otherwise return the same extents\nforever, and the mount would never finish. Let a fatal signal\ninterrupt the walk and fail the mount.\n\nRefusing read-write access to an empty extent is deliberate. It shows\nthat an old kernel took the last block but left the entry behind. If\nconsumed again, the entry returns an in-use block and turns into a huge\nbogus extent. Refusing the table before that\nhappens avoids this second allocation; the filesystem can still be\nmounted read-only. The check cannot detect every overlap that may\nalready exist in a damaged table.\n\nThis patch should be backported together with the previous one: that\npatch stops creating new empty extents, and this one rejects existing\nones before they are consumed again."
}
],
"providerMetadata": {
"dateUpdated": "2026-11-20T05:49:26.980Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/9f3df19234d2c180b9a99b0d3c2472e8fade5043"
},
{
"url": "https://git.kernel.org/stable/c/88401035fbfcad7067793455326262ac30633586"
},
{
"url": "https://git.kernel.org/stable/c/302eb1fa5be5e476a633d8ed0fd56ea5efa57374"
},
{
"url": "https://git.kernel.org/stable/c/e614c3e35a6699ed691b4d17e1ec4230e34aa3eb"
}
],
"title": "udf: check the unallocated space table when it is loaded",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99601",
"datePublished": "2026-11-20T05:49:26.980Z",
"dateReserved": "2026-09-25T10:25:14.424Z",
"dateUpdated": "2026-11-20T05:49:26.980Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-99601",
"date": "2026-11-20",
"epss": "0.00209",
"percentile": "0.11227"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/udf/super.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "9f3df19234d2c180b9a99b0d3c2472e8fade5043",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "88401035fbfcad7067793455326262ac30633586",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "302eb1fa5be5e476a633d8ed0fd56ea5efa57374",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
},
{
"lessThan": "e614c3e35a6699ed691b4d17e1ec4230e34aa3eb",
"status": "affected",
"version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/udf/super.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: check the unallocated space table when it is loaded\n\nudf_table_new_block() hands out the first block of the extent closest\nto its goal and trusts that the extent covers at least one whole block\ninside the partition. Nothing checks that. A zero-length extent makes\nit return the block the extent points at, which need not be free, and\nthe subtraction of one block then underflows the length into the type\nbits, turning the entry into a bogus continuation. An extent running\npast the end of the partition makes it return blocks behind the\npartition.\n\nSuch tables are not only found on crafted images: until the previous\ncommit, udf_table_new_block() itself left zero-length extents behind\nin tables written by mkudffs, and then converted them into extents\nrunning past the partition.\n\nCheck every extent once when the table is loaded, and refuse\nread-write access if one is empty, is not a whole number of blocks, or\ndoes not lie inside the partition, in the same way as for other\nallocation information the kernel cannot use. Check first that the\ntable is an Unallocated Space Entry at all: the walk starts at the\noffset of the allocation descriptors in one, and for a file entry that\noffset lies before the inode\u0027s in-memory copy of the descriptors.\nTreat a chain of allocation extent descriptors that leads back to\nitself the same way: the walk would otherwise return the same extents\nforever, and the mount would never finish. Let a fatal signal\ninterrupt the walk and fail the mount.\n\nRefusing read-write access to an empty extent is deliberate. It shows\nthat an old kernel took the last block but left the entry behind. If\nconsumed again, the entry returns an in-use block and turns into a huge\nbogus extent. Refusing the table before that\nhappens avoids this second allocation; the filesystem can still be\nmounted read-only. The check cannot detect every overlap that may\nalready exist in a damaged table.\n\nThis patch should be backported together with the previous one: that\npatch stops creating new empty extents, and this one rejects existing\nones before they are consumed again."
}
],
"id": "CVE-2026-99601",
"lastModified": "2026-11-20T06:17:52.077",
"metrics": {},
"published": "2026-11-20T06:17:52.077",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/302eb1fa5be5e476a633d8ed0fd56ea5efa57374"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/88401035fbfcad7067793455326262ac30633586"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/9f3df19234d2c180b9a99b0d3c2472e8fade5043"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/e614c3e35a6699ed691b4d17e1ec4230e34aa3eb"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-20T11:25:11+00:00",
"cve": "CVE-2026-99601",
"id": "CVE-2026-99601",
"initial_release_date": "2026-11-20T05:49:26.980000+00:00",
"product_status:known_affected": "204",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: kernel: Denial of service via crafted UDF filesystem image",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-99601.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.