CVE-2026-99108 (GCVE-0-2026-99108)
Vulnerability from cvelistv5
Published
2026-10-28 10:34
Modified
2026-10-28 10:34
Severity ?
VLAI Severity ?
EPSS score ?
Summary
In the Linux kernel, the following vulnerability has been resolved:
ntfs: fix FITRIM range alignment
ntfs_trim_fs() aligns the start of a free extent up to the device discard
granularity, but derives the discard length by aligning the original extent
length down. When the free extent start is not discard-aligned, adding that
length to the aligned start can extend the discard past the free extent and
into allocated clusters.
For example, with 4 KiB clusters and 32 KiB discard granularity, the free
extent [4 KiB, 36 KiB) becomes the discard range [32 KiB, 64 KiB), so
28 KiB beyond the free extent may be discarded.
Align the absolute end of the free extent down and derive the length from
the two aligned endpoints. Skip extents that contain no full discard unit.
Reproduced with a 4 KiB-cluster NTFS filesystem on scsi_debug configured
for 32 KiB discard granularity and read-zero-after-trim. Before this
change, FITRIM zeroed seven allocated 4 KiB clusters following an unaligned
32 KiB hole. With this change, the same data remains intact across FITRIM
and remount.
References
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/ntfs/bitmap.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "5e87da8ba8d3d647d89c754912e45c1f1a3bfc2e",
"status": "affected",
"version": "11ccc9107dc460de28af90fac1f42404d9802735",
"versionType": "git"
},
{
"lessThan": "03c6ecc4b4b13a3901f207152451fdd2d82e40c4",
"status": "affected",
"version": "11ccc9107dc460de28af90fac1f42404d9802735",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/ntfs/bitmap.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "7.1"
},
{
"lessThan": "7.1",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.13",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2.13",
"versionStartIncluding": "7.1",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3",
"versionStartIncluding": "7.1",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nntfs: fix FITRIM range alignment\n\nntfs_trim_fs() aligns the start of a free extent up to the device discard\ngranularity, but derives the discard length by aligning the original extent\nlength down. When the free extent start is not discard-aligned, adding that\nlength to the aligned start can extend the discard past the free extent and\ninto allocated clusters.\n\nFor example, with 4 KiB clusters and 32 KiB discard granularity, the free\nextent [4 KiB, 36 KiB) becomes the discard range [32 KiB, 64 KiB), so\n28 KiB beyond the free extent may be discarded.\n\nAlign the absolute end of the free extent down and derive the length from\nthe two aligned endpoints. Skip extents that contain no full discard unit.\n\nReproduced with a 4 KiB-cluster NTFS filesystem on scsi_debug configured\nfor 32 KiB discard granularity and read-zero-after-trim. Before this\nchange, FITRIM zeroed seven allocated 4 KiB clusters following an unaligned\n32 KiB hole. With this change, the same data remains intact across FITRIM\nand remount."
}
],
"providerMetadata": {
"dateUpdated": "2026-10-28T10:34:26.772Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/5e87da8ba8d3d647d89c754912e45c1f1a3bfc2e"
},
{
"url": "https://git.kernel.org/stable/c/03c6ecc4b4b13a3901f207152451fdd2d82e40c4"
}
],
"title": "ntfs: fix FITRIM range alignment",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-99108",
"datePublished": "2026-10-28T10:34:26.772Z",
"dateReserved": "2026-09-25T10:25:14.391Z",
"dateUpdated": "2026-10-28T10:34:26.772Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…