CVE-2026-72203 (GCVE-0-2026-72203)

Vulnerability from cvelistv5 – Published: 2026-08-15 05:54 – Updated: 2026-08-19 07:37
VLAI
Title
ntfs: skip extent mft records in writeback to prevent deadlock
Summary
In the Linux kernel, the following vulnerability has been resolved: ntfs: skip extent mft records in writeback to prevent deadlock This patch fixes the ABBA deadlock between extent_lock and extent mrec_lock triggered by xfstests generic/113, that occurs since the commit 6994acf33bae ("ntfs: use base mft_no when looking up base inode for extent record"). Path A (inode writeback): VFS writeback -> ntfs_write_inode() -> __ntfs_write_inode() -> mutex_lock(&ni->extent_lock) -> mutex_lock(&tni->mrec_lock) Path B (MFT folio writeback): VFS writeback of $MFT dirty folios -> ntfs_mft_writepages() -> ntfs_write_mft_block() -> ntfs_may_write_mft_record() -> holds one extent mrec_lock from a previous iteration -> tries to acquire another base inode extent_lock By removing all extent_lock and extent mrec_lock acquisition from the MFT folio writeback path, the ABBA lock ordering is eliminated: Path A: __ntfs_write_inode(): extent_lock -> mrec_lock Path B (removed): ntfs_write_mft_block(): mrec_lock -> extent_lock Path B is always redundant for extent records because: 1. mark_mft_record_dirty(ext_ni) does NOT dirty the MFT folio. It only sets NInoDirty(ext_ni) and marks the base VFS inode dirty via __mark_inode_dirty(I_DIRTY_DATASYNC), which triggers Path A. Therefore, normal extent modifications never create a situation where the MFT folio is dirty and Path B is not scheduled. 2. The MFT folio only gets dirtied via ntfs_mft_mark_dirty() inside ntfs_mft_record_alloc(). But all identified callers in attrib.c (ntfs_attr_add, ntfs_attr_record_move_away, ntfs_attr_make_non_resident, ntfs_attr_record_resize) follow through with mark_mft_record_dirty(), which triggers Path A to write the complete record. 3. ntfs_evict_big_inode() calls ntfs_commit_inode() before freeing extent inodes, ensuring all dirty extents are flushed via Path A before the base inode leaves the icache.
Severity
7.5 (High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Assigner
References
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < 7ffa8f3d30236e0ab897c30bdb01224ff1fe1c89 (git)
Affected: 1e9ea7e04472d4e5e12e58c881eaacfb3e49b669 , < f831ab09d521898bf1dd99bf5adfd630ea1428e3 (git)
Affected: 1e9ea7e04472d4e5e12e58c881eaacfb3e49b669 , < 76bc14c7097ff678b2b5dbfd4fa33b46897d87ce (git)
guessed Create a notification for this product.
Linux Linux Affected: 2.6.12
Affected: 7.1
Unaffected: 0 , < 2.6.12 (semver)
Unaffected: 6.9 , < 7.1 (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/ntfs/mft.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "7ffa8f3d30236e0ab897c30bdb01224ff1fe1c89",
              "status": "affected",
              "version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
              "versionType": "git"
            },
            {
              "lessThan": "f831ab09d521898bf1dd99bf5adfd630ea1428e3",
              "status": "affected",
              "version": "1e9ea7e04472d4e5e12e58c881eaacfb3e49b669",
              "versionType": "git"
            },
            {
              "lessThan": "76bc14c7097ff678b2b5dbfd4fa33b46897d87ce",
              "status": "affected",
              "version": "1e9ea7e04472d4e5e12e58c881eaacfb3e49b669",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/ntfs/mft.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "2.6.12"
            },
            {
              "status": "affected",
              "version": "7.1"
            },
            {
              "lessThan": "2.6.12",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThan": "7.1",
              "status": "unaffected",
              "version": "6.9",
              "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": "6.9",
                  "versionStartIncluding": "2.6.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1.5",
                  "versionStartIncluding": "7.1",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2",
                  "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: skip extent mft records in writeback to prevent deadlock\n\nThis patch fixes the ABBA deadlock between extent_lock and extent\nmrec_lock triggered by xfstests generic/113, that occurs since the commit\n6994acf33bae (\"ntfs: use base mft_no when looking up base inode for\n\t\textent record\").\n\nPath A (inode writeback):\n  VFS writeback\n    -\u003e ntfs_write_inode()\n      -\u003e __ntfs_write_inode()\n        -\u003e mutex_lock(\u0026ni-\u003eextent_lock)\n        -\u003e mutex_lock(\u0026tni-\u003emrec_lock)\n\nPath B (MFT folio writeback):\n  VFS writeback of $MFT dirty folios\n    -\u003e ntfs_mft_writepages()\n      -\u003e ntfs_write_mft_block()\n        -\u003e ntfs_may_write_mft_record()\n          -\u003e holds one extent mrec_lock from a previous iteration\n          -\u003e tries to acquire another base inode extent_lock\n\nBy removing all extent_lock and extent mrec_lock acquisition from the MFT\nfolio writeback path, the ABBA lock ordering is eliminated:\n\nPath A: __ntfs_write_inode(): extent_lock -\u003e mrec_lock\nPath B (removed): ntfs_write_mft_block(): mrec_lock -\u003e extent_lock\n\nPath B is always redundant for extent records because:\n\n1. mark_mft_record_dirty(ext_ni) does NOT dirty the MFT folio.\n   It only sets NInoDirty(ext_ni) and marks the base VFS inode dirty\n   via __mark_inode_dirty(I_DIRTY_DATASYNC), which triggers Path A.\n   Therefore, normal extent modifications never create a situation where\n   the MFT folio is dirty and Path B is not scheduled.\n\n2. The MFT folio only gets dirtied via ntfs_mft_mark_dirty() inside\n   ntfs_mft_record_alloc(). But all identified callers in attrib.c\n   (ntfs_attr_add, ntfs_attr_record_move_away,\n   ntfs_attr_make_non_resident, ntfs_attr_record_resize) follow through\n   with mark_mft_record_dirty(), which triggers Path A to write the\n   complete record.\n\n3. ntfs_evict_big_inode() calls ntfs_commit_inode() before freeing extent\n   inodes, ensuring all dirty extents are flushed via Path A before the\n   base inode leaves the icache."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.5,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:N - The ABBA deadlock is reachable through concurrent VFS writeback on an rw-mounted NTFS volume; ntfs registers ntfs_export_ops, so nfsd/ksmbd remote WRITE/CLOSE/fsync RPCs on an exported NTFS share hit __ntfs_write_inode() and ntfs_mft_writepages() the same as local aio/write syscalls.\nAC:L - xfstests generic/113 (aio-stress with concurrent O_DIRECT/O_SYNC writes) reliably reproduces the hang; an attacker controls both lock-order participants by issuing parallel file metadata writes and sync/writeback pressure without races or attacker-independent memory layout.\nPR:N - Exploitation needs only write access to an rw-mounted or NFS/SMB-exported NTFS volume to drive ntfs_mft_record_alloc and concurrent writeback; no CAP_SYS_ADMIN, root, or init-namespace privileges on the server are required to deadlock the writeback paths.\nUI:N - Once an NTFS volume is rw-mounted (dual-boot partition, removable media, loop mount, or network export), the attacker issues the concurrent writes itself; no additional victim clicks, opens, or cooperative actions are required beyond that standing configuration.\nS:U - The circular mutex wait between extent_lock and extent mrec_lock only hangs kernel writeback and I/O worker threads within the host kernel security authority; it does not cross VM, container, IOMMU, or other security-boundary scopes.\nC:N - This is a deterministic lock-order inversion with no out-of-bounds access, use-after-free, or information disclosure; blocked threads wait on mutexes without reading attacker-controlled freed memory or leaking kernel pointers.\nI:N - The defect prevents completion of metadata writeback by deadlocking mutex acquisition; it does not perform attacker-controlled memory writes, corrupt on-disk NTFS structures, or provide a metadata modification primitive beyond denying forward progress.\nA:H - The ABBA deadlock between inode writeback (extent_lock then extent mrec_lock) and $MFT folio writeback (held mrec_lock then extent_lock) hangs kworker writeback and sync/fsync callers indefinitely, causing system-wide I/O denial of service."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-19T07:37:27.158Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/7ffa8f3d30236e0ab897c30bdb01224ff1fe1c89"
        },
        {
          "url": "https://git.kernel.org/stable/c/f831ab09d521898bf1dd99bf5adfd630ea1428e3"
        },
        {
          "url": "https://git.kernel.org/stable/c/76bc14c7097ff678b2b5dbfd4fa33b46897d87ce"
        }
      ],
      "title": "ntfs: skip extent mft records in writeback to prevent deadlock",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-72203",
    "datePublished": "2026-08-15T05:54:00.321Z",
    "dateReserved": "2026-08-09T03:40:39.912Z",
    "dateUpdated": "2026-08-19T07:37:27.158Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-72203",
      "date": "2026-08-24",
      "epss": "0.00576",
      "percentile": "0.4487"
    },
    "microsoft_vex": {
      "current_release_date": "2026-08-23T14:42:59.000Z",
      "cve": "CVE-2026-72203",
      "id": "msrc_CVE-2026-72203",
      "initial_release_date": "2026-08-23T14:42:59.000Z",
      "product_status:known_affected": "1",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "ntfs: skip extent mft records in writeback to prevent deadlock",
      "url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-72203.json",
      "version": "1"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-72203\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-08-15T06:21:38.970\",\"lastModified\":\"2026-08-19T08:17:13.473\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nntfs: skip extent mft records in writeback to prevent deadlock\\n\\nThis patch fixes the ABBA deadlock between extent_lock and extent\\nmrec_lock triggered by xfstests generic/113, that occurs since the commit\\n6994acf33bae (\\\"ntfs: use base mft_no when looking up base inode for\\n\\t\\textent record\\\").\\n\\nPath A (inode writeback):\\n  VFS writeback\\n    -\u003e ntfs_write_inode()\\n      -\u003e __ntfs_write_inode()\\n        -\u003e mutex_lock(\u0026ni-\u003eextent_lock)\\n        -\u003e mutex_lock(\u0026tni-\u003emrec_lock)\\n\\nPath B (MFT folio writeback):\\n  VFS writeback of $MFT dirty folios\\n    -\u003e ntfs_mft_writepages()\\n      -\u003e ntfs_write_mft_block()\\n        -\u003e ntfs_may_write_mft_record()\\n          -\u003e holds one extent mrec_lock from a previous iteration\\n          -\u003e tries to acquire another base inode extent_lock\\n\\nBy removing all extent_lock and extent mrec_lock acquisition from the MFT\\nfolio writeback path, the ABBA lock ordering is eliminated:\\n\\nPath A: __ntfs_write_inode(): extent_lock -\u003e mrec_lock\\nPath B (removed): ntfs_write_mft_block(): mrec_lock -\u003e extent_lock\\n\\nPath B is always redundant for extent records because:\\n\\n1. mark_mft_record_dirty(ext_ni) does NOT dirty the MFT folio.\\n   It only sets NInoDirty(ext_ni) and marks the base VFS inode dirty\\n   via __mark_inode_dirty(I_DIRTY_DATASYNC), which triggers Path A.\\n   Therefore, normal extent modifications never create a situation where\\n   the MFT folio is dirty and Path B is not scheduled.\\n\\n2. The MFT folio only gets dirtied via ntfs_mft_mark_dirty() inside\\n   ntfs_mft_record_alloc(). But all identified callers in attrib.c\\n   (ntfs_attr_add, ntfs_attr_record_move_away,\\n   ntfs_attr_make_non_resident, ntfs_attr_record_resize) follow through\\n   with mark_mft_record_dirty(), which triggers Path A to write the\\n   complete record.\\n\\n3. ntfs_evict_big_inode() calls ntfs_commit_inode() before freeing extent\\n   inodes, ensuring all dirty extents are flushed via Path A before the\\n   base inode leaves the icache.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"fs/ntfs/mft.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2\",\"lessThan\":\"7ffa8f3d30236e0ab897c30bdb01224ff1fe1c89\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"1e9ea7e04472d4e5e12e58c881eaacfb3e49b669\",\"lessThan\":\"f831ab09d521898bf1dd99bf5adfd630ea1428e3\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"1e9ea7e04472d4e5e12e58c881eaacfb3e49b669\",\"lessThan\":\"76bc14c7097ff678b2b5dbfd4fa33b46897d87ce\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"fs/ntfs/mft.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"2.6.12\",\"status\":\"affected\"},{\"version\":\"7.1\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"2.6.12\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.9\",\"lessThan\":\"7.1\",\"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:N/I:N/A:H\",\"baseScore\":7.5,\"baseSeverity\":\"HIGH\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":3.9,\"impactScore\":3.6}]},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/76bc14c7097ff678b2b5dbfd4fa33b46897d87ce\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/7ffa8f3d30236e0ab897c30bdb01224ff1fe1c89\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/f831ab09d521898bf1dd99bf5adfd630ea1428e3\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}",
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-08-18T11:08:27+00:00",
      "cve": "CVE-2026-72203",
      "id": "CVE-2026-72203",
      "initial_release_date": "2026-08-15T00:00:00+00:00",
      "product_status:known_not_affected": "274",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: ntfs: skip extent mft records in writeback to prevent deadlock",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-72203.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-08-21T00:42:35Z",
      "cve": "CVE-2026-72203",
      "id": "CVE-2026-72203",
      "initial_release_date": "2026-08-21T00:42:35Z",
      "product_status:known_affected": "255",
      "product_status:known_not_affected": "29",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2026-72203",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2026-72203.json",
      "version": "2"
    }
  }
}



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.