CVE-2025-40067 (GCVE-0-2025-40067)
Vulnerability from cvelistv5 – Published: 2025-10-28 11:48 – Updated: 2025-12-01 06:17
VLAI?
Summary
In the Linux kernel, the following vulnerability has been resolved:
fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist
Index allocation requires at least one bit in the $BITMAP attribute to
track usage of index entries. If the bitmap is empty while index blocks
are already present, this reflects on-disk corruption.
syzbot triggered this condition using a malformed NTFS image. During a
rename() operation involving a long filename (which spans multiple
index entries), the empty bitmap allowed the name to be added without
valid tracking. Subsequent deletion of the original entry failed with
-ENOENT, due to unexpected index state.
Reject such cases by verifying that the bitmap is not empty when index
blocks exist.
Severity ?
No CVSS data available.
Assigner
References
Impacted products
| Vendor | Product | Version | ||
|---|---|---|---|---|
| Linux | Linux |
Affected:
b35a50d639ca5259466ef5fea85529bb4fb17d5b , < 978aac54e93ea35aab20b32ae393d3d33964e7ae
(git)
Affected: 3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dcc , < be66551da203862c689c12e1d35ce87217c017c1 (git) Affected: d99208b91933fd2a58ed9ed321af07dacd06ddc3 , < 039ddf353cc33f6546a87ec1ac3210637d714bec (git) Affected: d99208b91933fd2a58ed9ed321af07dacd06ddc3 , < 0dc7117da8f92dd5fe077d712a756eccbe377d40 (git) Affected: 358d4f821c03add421a4c49290538a705852ccf1 (git) Affected: a285395020780adac1ffbc844069c3d700bf007a (git) |
||
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/ntfs3/index.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "978aac54e93ea35aab20b32ae393d3d33964e7ae",
"status": "affected",
"version": "b35a50d639ca5259466ef5fea85529bb4fb17d5b",
"versionType": "git"
},
{
"lessThan": "be66551da203862c689c12e1d35ce87217c017c1",
"status": "affected",
"version": "3ed2cc6a6e93fbeb8c0cafce1e7fb1f64a331dcc",
"versionType": "git"
},
{
"lessThan": "039ddf353cc33f6546a87ec1ac3210637d714bec",
"status": "affected",
"version": "d99208b91933fd2a58ed9ed321af07dacd06ddc3",
"versionType": "git"
},
{
"lessThan": "0dc7117da8f92dd5fe077d712a756eccbe377d40",
"status": "affected",
"version": "d99208b91933fd2a58ed9ed321af07dacd06ddc3",
"versionType": "git"
},
{
"status": "affected",
"version": "358d4f821c03add421a4c49290538a705852ccf1",
"versionType": "git"
},
{
"status": "affected",
"version": "a285395020780adac1ffbc844069c3d700bf007a",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/ntfs3/index.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.17"
},
{
"lessThan": "6.17",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.112",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.53",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.17.*",
"status": "unaffected",
"version": "6.17.3",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.18",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.6.112",
"versionStartIncluding": "6.6.102",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.53",
"versionStartIncluding": "6.12.42",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.17.3",
"versionStartIncluding": "6.17",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18",
"versionStartIncluding": "6.17",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.15.10",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "6.16.1",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist\n\nIndex allocation requires at least one bit in the $BITMAP attribute to\ntrack usage of index entries. If the bitmap is empty while index blocks\nare already present, this reflects on-disk corruption.\n\nsyzbot triggered this condition using a malformed NTFS image. During a\nrename() operation involving a long filename (which spans multiple\nindex entries), the empty bitmap allowed the name to be added without\nvalid tracking. Subsequent deletion of the original entry failed with\n-ENOENT, due to unexpected index state.\n\nReject such cases by verifying that the bitmap is not empty when index\nblocks exist."
}
],
"providerMetadata": {
"dateUpdated": "2025-12-01T06:17:18.363Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/978aac54e93ea35aab20b32ae393d3d33964e7ae"
},
{
"url": "https://git.kernel.org/stable/c/be66551da203862c689c12e1d35ce87217c017c1"
},
{
"url": "https://git.kernel.org/stable/c/039ddf353cc33f6546a87ec1ac3210637d714bec"
},
{
"url": "https://git.kernel.org/stable/c/0dc7117da8f92dd5fe077d712a756eccbe377d40"
}
],
"title": "fs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2025-40067",
"datePublished": "2025-10-28T11:48:37.034Z",
"dateReserved": "2025-04-16T07:20:57.159Z",
"dateUpdated": "2025-12-01T06:17:18.363Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": "{\"cve\":{\"id\":\"CVE-2025-40067\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-10-28T12:15:41.167\",\"lastModified\":\"2025-10-30T15:05:32.197\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nfs/ntfs3: reject index allocation if $BITMAP is empty but blocks exist\\n\\nIndex allocation requires at least one bit in the $BITMAP attribute to\\ntrack usage of index entries. If the bitmap is empty while index blocks\\nare already present, this reflects on-disk corruption.\\n\\nsyzbot triggered this condition using a malformed NTFS image. During a\\nrename() operation involving a long filename (which spans multiple\\nindex entries), the empty bitmap allowed the name to be added without\\nvalid tracking. Subsequent deletion of the original entry failed with\\n-ENOENT, due to unexpected index state.\\n\\nReject such cases by verifying that the bitmap is not empty when index\\nblocks exist.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/039ddf353cc33f6546a87ec1ac3210637d714bec\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/0dc7117da8f92dd5fe077d712a756eccbe377d40\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/978aac54e93ea35aab20b32ae393d3d33964e7ae\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/be66551da203862c689c12e1d35ce87217c017c1\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
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.
Loading…
Loading…