{"api_version":"1","generated_at":"2026-10-29T07:57:50+00:00","cve":"CVE-2026-99108","urls":{"html":"https://cve.report/CVE-2026-99108","api":"https://cve.report/api/cve/CVE-2026-99108.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99108","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99108"},"summary":{"title":"ntfs: fix FITRIM range alignment","description":"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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-10-28 11:17:30","updated_at":"2026-10-28 11:17:30"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/5e87da8ba8d3d647d89c754912e45c1f1a3bfc2e","name":"https://git.kernel.org/stable/c/5e87da8ba8d3d647d89c754912e45c1f1a3bfc2e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/03c6ecc4b4b13a3901f207152451fdd2d82e40c4","name":"https://git.kernel.org/stable/c/03c6ecc4b4b13a3901f207152451fdd2d82e40c4","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99108","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99108","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 11ccc9107dc460de28af90fac1f42404d9802735 5e87da8ba8d3d647d89c754912e45c1f1a3bfc2e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 11ccc9107dc460de28af90fac1f42404d9802735 03c6ecc4b4b13a3901f207152451fdd2d82e40c4 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7.1","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.13 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"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"},"nvd":{"publishedDate":"2026-10-28 11:17:30","lastModifiedDate":"2026-10-28 11:17:30","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"99108","Ordinal":"1","Title":"ntfs: fix FITRIM range alignment","CVE":"CVE-2026-99108","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99108","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"ntfs: fix FITRIM range alignment"}]}}}