{"api_version":"1","generated_at":"2026-10-01T03:09:23+00:00","cve":"CVE-2026-98139","urls":{"html":"https://cve.report/CVE-2026-98139","api":"https://cve.report/api/cve/CVE-2026-98139.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-98139","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-98139"},"summary":{"title":"ntfs: only count successfully cleared runs when freeing clusters","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nntfs: only count successfully cleared runs when freeing clusters\n\nntfs_cluster_free_from_rl_nolock() adds a run's length to nr_freed\nwhenever the error bookkeeping condition is false, which includes\ncases where ntfs_bitmap_clear_run() actually failed - e.g. a second\nrun failing with the same errno as an earlier one, or any failure\nafter a non-ENOMEM error was already recorded. Since a failed\nntfs_bitmap_clear_run() rolls back its partial modifications, no\nbits were cleared for that run, yet its length still inflates\nvol->free_clusters, corrupting statfs output and the allocator's\nfree space gate.\n\nOnly count runs whose bitmap clear succeeded.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-25 11:17:45","updated_at":"2026-09-30 14:10:59"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/7eb97d8828e7758b9c81277f7802e740a800f78a","name":"https://git.kernel.org/stable/c/7eb97d8828e7758b9c81277f7802e740a800f78a","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/be9e89ccb8e52a3e4b67feeb03ebd8133091dc7e","name":"https://git.kernel.org/stable/c/be9e89ccb8e52a3e4b67feeb03ebd8133091dc7e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-98139","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98139","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 11ccc9107dc460de28af90fac1f42404d9802735 7eb97d8828e7758b9c81277f7802e740a800f78a git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 11ccc9107dc460de28af90fac1f42404d9802735 be9e89ccb8e52a3e4b67feeb03ebd8133091dc7e 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.7 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"98139","cve":"CVE-2026-98139","epss":"0.001770000","percentile":"0.065080000","score_date":"2026-09-27","updated_at":"2026-09-28 00:02:24"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/ntfs/lcnalloc.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"7eb97d8828e7758b9c81277f7802e740a800f78a","status":"affected","version":"11ccc9107dc460de28af90fac1f42404d9802735","versionType":"git"},{"lessThan":"be9e89ccb8e52a3e4b67feeb03ebd8133091dc7e","status":"affected","version":"11ccc9107dc460de28af90fac1f42404d9802735","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/ntfs/lcnalloc.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.7","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.7","versionStartIncluding":"7.1","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc2","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: only count successfully cleared runs when freeing clusters\n\nntfs_cluster_free_from_rl_nolock() adds a run's length to nr_freed\nwhenever the error bookkeeping condition is false, which includes\ncases where ntfs_bitmap_clear_run() actually failed - e.g. a second\nrun failing with the same errno as an earlier one, or any failure\nafter a non-ENOMEM error was already recorded. Since a failed\nntfs_bitmap_clear_run() rolls back its partial modifications, no\nbits were cleared for that run, yet its length still inflates\nvol->free_clusters, corrupting statfs output and the allocator's\nfree space gate.\n\nOnly count runs whose bitmap clear succeeded."}],"providerMetadata":{"dateUpdated":"2026-09-25T10:36:15.974Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/7eb97d8828e7758b9c81277f7802e740a800f78a"},{"url":"https://git.kernel.org/stable/c/be9e89ccb8e52a3e4b67feeb03ebd8133091dc7e"}],"title":"ntfs: only count successfully cleared runs when freeing clusters","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-98139","datePublished":"2026-09-25T10:36:15.974Z","dateReserved":"2026-09-25T10:25:14.319Z","dateUpdated":"2026-09-25T10:36:15.974Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-25 11:17:45","lastModifiedDate":"2026-09-30 14:10:59","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"98139","Ordinal":"1","Title":"ntfs: only count successfully cleared runs when freeing clusters","CVE":"CVE-2026-98139","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"98139","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nntfs: only count successfully cleared runs when freeing clusters\n\nntfs_cluster_free_from_rl_nolock() adds a run's length to nr_freed\nwhenever the error bookkeeping condition is false, which includes\ncases where ntfs_bitmap_clear_run() actually failed - e.g. a second\nrun failing with the same errno as an earlier one, or any failure\nafter a non-ENOMEM error was already recorded. Since a failed\nntfs_bitmap_clear_run() rolls back its partial modifications, no\nbits were cleared for that run, yet its length still inflates\nvol->free_clusters, corrupting statfs output and the allocator's\nfree space gate.\n\nOnly count runs whose bitmap clear succeeded.","Type":"Description","Title":"ntfs: only count successfully cleared runs when freeing clusters"}]}}}