Skip to content
Heist/ feed
Back to feed
UnratedFix available

ntfs: only count successfully cleared runs when freeing clusters

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: ntfs: only count successfully cleared runs when freeing clusters ntfs_cluster_free_from_rl_nolock() adds a run's length to nr_freed whenever the error bookkeeping condition is false, which includes cases where ntfs_bitmap_clear_run() actually failed - e.g. a second run failing with the same errno as an earlier one, or any failure after a non-ENOMEM error was already recorded. Since a failed ntfs_bitmap_clear_run() rolls back its partial modifications, no bits were cleared for that run, yet its length still inflates vol->free_clusters, corrupting statfs output and the allocator's free space gate. Only count runs whose bitmap clear succeeded.

Products
Kernel
Affected versions
Not specified
Fixed versions
7.2.7
CVEs
CVE-2026-98139
Confirmed fixed CVEs
Not specified
Updated in this feed
7 Nov 2026, 00:49 UTC · Revision 1

Source evidence

ntfs: only count successfully cleared runs when freeing clusters

core-osv · Original source

Published 25 Sept 2026, 10:36 UTC

In the Linux kernel, the following vulnerability has been resolved: ntfs: only count successfully cleared runs when freeing clusters ntfs_cluster_free_from_rl_nolock() adds a run's length to nr_freed whenever the error bookkeeping condition is false, which includes cases where ntfs_bitmap_clear_run() actually failed - e.g. a second run failing with the same errno as an earlier one, or any failure after a non-ENOMEM error was already recorded. Since a failed ntfs_bitmap_clear_run() rolls back its partial modifications, no bits were cleared for that run, yet its length still inflates vol->free_clusters, corrupting statfs output and the allocator's free space gate. Only count runs whose bitmap clear succeeded.

osv:CVE-2026-98139

Kernel

Fixed versions: 7.2.7

Complete source record
{
  "id": "700fcf2327747b9d627a834eea73d4c08aa23f66772cfc4f051a30a569439984",
  "url": "https://osv.dev/vulnerability/CVE-2026-98139",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "ntfs: only count successfully cleared runs when freeing clusters",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: ntfs: only count successfully cleared runs when freeing clusters ntfs_cluster_free_from_rl_nolock() adds a run's length to nr_freed whenever the error bookkeeping condition is false, which includes cases where ntfs_bitmap_clear_run() actually failed - e.g. a second run failing with the same errno as an earlier one, or any failure after a non-ENOMEM error was already recorded. Since a failed ntfs_bitmap_clear_run() rolls back its partial modifications, no bits were cleared for that run, yet its length still inflates vol->free_clusters, corrupting statfs output and the allocator's free space gate. Only count runs whose bitmap clear succeeded.",
    "evidence": "osv:CVE-2026-98139",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "7.2.7",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2026-98139",
      "aliases": [
        "CVE-2026-98139"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "11ccc9107dc460de28af90fac1f42404d9802735"
                },
                {
                  "fixed": "7eb97d8828e7758b9c81277f7802e740a800f78a"
                },
                {
                  "fixed": "be9e89ccb8e52a3e4b67feeb03ebd8133091dc7e"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98139.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "7.1.0"
                },
                {
                  "fixed": "7.2.7"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98139.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:48.518855528Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/7eb97d8828e7758b9c81277f7802e740a800f78a",
        "https://git.kernel.org/stable/c/be9e89ccb8e52a3e4b67feeb03ebd8133091dc7e",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98139.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-98139",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98139.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-98139",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 516746,
  "published_at": "2026-09-25T10:36:15.974+00:00"
}