CVE-2026-72477 (GCVE-0-2026-72477)

Vulnerability from cvelistv5 – Published: 2026-08-15 05:57 – Updated: 2026-08-17 05:44
VLAI
Title
fs/ntfs3: call _ntfs_bad_inode() when failing to rename
Summary
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: call _ntfs_bad_inode() when failing to rename It is safe to call _ntfs_bad_inode on live inodes since: commit 519b078998ce ("fs/ntfs3: Exclude call make_bad_inode for live nodes.") The WARN_ON was added when it wasn't safe by: commit d99208b91933 ("fs/ntfs3: cancle set bad inode after removing name fails") Replace the WARN_ON with a call to _ntfs_bad_inode() to prevent further operations on the inconsistent inode.
Severity
9.8 (Critical)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Assigner
References
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: 519b078998ce6e729f98dccf35505b4756985d11 , < ff825bf0521f6da2f30878cbad18ab7b341bc31b (git)
Affected: 519b078998ce6e729f98dccf35505b4756985d11 , < e8ed78f40eecd0176fda71d673f6957c98e7ffbe (git)
guessed Create a notification for this product.
Linux Linux Affected: 6.17
Unaffected: 0 , < 6.17 (semver)
Unaffected: 7.1.5 , ≤ 7.1.* (semver)
Unaffected: 7.2 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/ntfs3/frecord.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "ff825bf0521f6da2f30878cbad18ab7b341bc31b",
              "status": "affected",
              "version": "519b078998ce6e729f98dccf35505b4756985d11",
              "versionType": "git"
            },
            {
              "lessThan": "e8ed78f40eecd0176fda71d673f6957c98e7ffbe",
              "status": "affected",
              "version": "519b078998ce6e729f98dccf35505b4756985d11",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/ntfs3/frecord.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": "7.1.*",
              "status": "unaffected",
              "version": "7.1.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1.5",
                  "versionStartIncluding": "6.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2",
                  "versionStartIncluding": "6.17",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: call _ntfs_bad_inode() when failing to rename\n\nIt is safe to call _ntfs_bad_inode on live inodes since:\n  commit 519b078998ce (\"fs/ntfs3: Exclude call make_bad_inode for live nodes.\")\n\nThe WARN_ON was added when it wasn\u0027t safe by:\n  commit d99208b91933 (\"fs/ntfs3: cancle set bad inode after removing name fails\")\n\nReplace the WARN_ON with a call to _ntfs_bad_inode() to prevent further\noperations on the inconsistent inode."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 9.8,
            "baseSeverity": "CRITICAL",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:N - ntfs3 registers export_operations and rename on an NFS- or SMB-exported NTFS volume reaches ni_rename() through nfsd/ksmbd vfs_rename without any local syscall; hybrid NAS and Windows/Linux file-server deployments are a reasonable high-impact reach path for this VFS rename flaw.\nAC:L - An attacker controls the on-disk NTFS layout and rename arguments so ni_add_name succeeds and both ni_remove_name steps fail deterministically; syzkaller reproduces this with a crafted loop image and no races or victim-specific timing outside attacker influence.\nPR:N - Exploitation needs only permission to rename on an exported NTFS share (including guest/anonymous NFS or SMB write access) or to supply removable media later mounted by the host; no init-namespace root, CAP_SYS_ADMIN, or other elevated host credentials are required.\nUI:N - Once an administrator has mounted and exported the NTFS volume (or automounted dual-boot/shared storage), the attacker triggers the flawed rename directly; no further victim clicks, file opens, or cooperative actions are needed beyond that standing configuration.\nS:U - Impact is kernel heap/metadata corruption and denial of service within the same kernel security authority; this is standard local or network filesystem exploitation, not a VM escape, IOMMU bypass, or cross-scope sandbox breakout.\nC:H - Leaving the inode operable after a failed rename rollback preserves inconsistent MFT/directory index state; subsequent lookups and index walks parse attacker-influenced corrupt metadata, matching ntfs3 guidance to score metadata corruption that can yield kernel memory disclosure as High.\nI:H - Without ni_bad set, further writes, unlinks, and renames continue against mismatched $FILE_NAME and $I30 state, propagating attacker-steerable directory/MFT corruption and heap metadata damage that can be leveraged for arbitrary kernel writes or control-flow hijack.\nA:H - The vulnerable path emits WARN_ON in ni_rename (kernel panic on panic_on_warn) and syzbot also hit a kernel paging fault in folio_wait_bit_common after follow-on operations on the inconsistent inode; any kernel oops, hang, or panic from continued use scores Availability High."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-17T05:44:41.716Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/ff825bf0521f6da2f30878cbad18ab7b341bc31b"
        },
        {
          "url": "https://git.kernel.org/stable/c/e8ed78f40eecd0176fda71d673f6957c98e7ffbe"
        }
      ],
      "title": "fs/ntfs3: call _ntfs_bad_inode() when failing to rename",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-72477",
    "datePublished": "2026-08-15T05:57:17.035Z",
    "dateReserved": "2026-08-09T03:40:39.934Z",
    "dateUpdated": "2026-08-17T05:44:41.716Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-72477",
      "date": "2026-08-24",
      "epss": "0.00516",
      "percentile": "0.41586"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-72477\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-08-15T06:22:21.867\",\"lastModified\":\"2026-08-17T06:19:15.750\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nfs/ntfs3: call _ntfs_bad_inode() when failing to rename\\n\\nIt is safe to call _ntfs_bad_inode on live inodes since:\\n  commit 519b078998ce (\\\"fs/ntfs3: Exclude call make_bad_inode for live nodes.\\\")\\n\\nThe WARN_ON was added when it wasn\u0027t safe by:\\n  commit d99208b91933 (\\\"fs/ntfs3: cancle set bad inode after removing name fails\\\")\\n\\nReplace the WARN_ON with a call to _ntfs_bad_inode() to prevent further\\noperations on the inconsistent inode.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"fs/ntfs3/frecord.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"519b078998ce6e729f98dccf35505b4756985d11\",\"lessThan\":\"ff825bf0521f6da2f30878cbad18ab7b341bc31b\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"519b078998ce6e729f98dccf35505b4756985d11\",\"lessThan\":\"e8ed78f40eecd0176fda71d673f6957c98e7ffbe\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"fs/ntfs3/frecord.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"6.17\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"6.17\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.1.5\",\"lessThanOrEqual\":\"7.1.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.2\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H\",\"baseScore\":9.8,\"baseSeverity\":\"CRITICAL\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":3.9,\"impactScore\":5.9}]},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/e8ed78f40eecd0176fda71d673f6957c98e7ffbe\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/ff825bf0521f6da2f30878cbad18ab7b341bc31b\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}",
    "redhat_vex": {
      "current_release_date": "2026-08-19T18:18:56+00:00",
      "cve": "CVE-2026-72477",
      "id": "CVE-2026-72477",
      "initial_release_date": "2026-08-15T00:00:00+00:00",
      "product_status:known_not_affected": "1",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: fs/ntfs3: call _ntfs_bad_inode() when failing to rename",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-72477.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

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.


Detection rules are retrieved from Rulezet.