Vulnerability-Lookup

GHSA-7XMJ-MQHM-5492

Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-15 06:32

Details

In the Linux kernel, the following vulnerability has been resolved:

ntfs: fix mrec_lock ABBA deadlock in rename

ntfs_file_fsync(), ntfs_dir_fsync() and __ntfs_write_inode() lock an inode's mrec_lock before taking the mrec_lock of its parent directory.

ntfs_rename() takes old_ni->mrec_lock and old_dir_ni->mrec_lock before taking new_ni->mrec_lock for an existing target, or new_dir_ni->mrec_lock for a cross-directory rename. This can deadlock when ntfs_file_fsync() or __ntfs_write_inode() holds the target inode, or when ntfs_dir_fsync() holds a child target directory, while rename() holds the parent directory and waits for the target.

Fix this by locking the existing target inode before taking any parent directory mrec_lock. For cross-directory renames where the target parent is a descendant of the source parent, lock the target parent before the source parent so the directory order matches the child-to-parent order used by ntfs_file_fsync(), ntfs_dir_fsync(), and __ntfs_write_inode().

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-72190"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-15T06:21:37Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nntfs: fix mrec_lock ABBA deadlock in rename\n\nntfs_file_fsync(), ntfs_dir_fsync() and __ntfs_write_inode() lock an\ninode\u0027s mrec_lock before taking the mrec_lock of its parent directory.\n\nntfs_rename() takes old_ni-\u003emrec_lock and old_dir_ni-\u003emrec_lock\nbefore taking new_ni-\u003emrec_lock for an existing target, or\nnew_dir_ni-\u003emrec_lock for a cross-directory rename.\nThis can deadlock when ntfs_file_fsync() or __ntfs_write_inode() holds\nthe target inode, or when ntfs_dir_fsync() holds a child target\ndirectory, while rename() holds the parent directory and waits for the\ntarget.\n\nFix this by locking the existing target inode before taking any parent\ndirectory mrec_lock. For cross-directory renames where the target parent\nis a descendant of the source parent, lock the target parent before the\nsource parent so the directory order matches the child-to-parent order used\nby ntfs_file_fsync(), ntfs_dir_fsync(), and __ntfs_write_inode().",
  "id": "GHSA-7xmj-mqhm-5492",
  "modified": "2026-08-15T06:32:15Z",
  "published": "2026-08-15T06:32:15Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72190"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b3d09502b80dfe0bab9090ca532710da389f6c7f"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/eb94f5a41a193a425e09a63cb75dffd151d8f42e"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-72190 (GCVE-0-2026-72190)

Vulnerability from cvelistv5 – Published: 2026-08-15 05:53 – Updated: 2026-08-17 05:09

Title

ntfs: fix mrec_lock ABBA deadlock in rename

Summary

In the Linux kernel, the following vulnerability has been resolved: ntfs: fix mrec_lock ABBA deadlock in rename ntfs_file_fsync(), ntfs_dir_fsync() and __ntfs_write_inode() lock an inode's mrec_lock before taking the mrec_lock of its parent directory. ntfs_rename() takes old_ni->mrec_lock and old_dir_ni->mrec_lock before taking new_ni->mrec_lock for an existing target, or new_dir_ni->mrec_lock for a cross-directory rename. This can deadlock when ntfs_file_fsync() or __ntfs_write_inode() holds the target inode, or when ntfs_dir_fsync() holds a child target directory, while rename() holds the parent directory and waits for the target. Fix this by locking the existing target inode before taking any parent directory mrec_lock. For cross-directory renames where the target parent is a descendant of the source parent, lock the target parent before the source parent so the directory order matches the child-to-parent order used by ntfs_file_fsync(), ntfs_dir_fsync(), and __ntfs_write_inode().

Severity

No CVSS data available.

Assigner

Linux CNA under the mitre root

CNA scorecard D 53/100 over 6992 records in the last 180 days details

References

2 references

URL	Tags
https://git.kernel.org/stable/c/b3d09502b80dfe0ba…
https://git.kernel.org/stable/c/eb94f5a41a193a425…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: af0db57d4293cc9fe6ce99fb5592dc2652228c9d , < b3d09502b80dfe0bab9090ca532710da389f6c7f (git) Affected: af0db57d4293cc9fe6ce99fb5592dc2652228c9d , < eb94f5a41a193a425e09a63cb75dffd151d8f42e (git)
Linux	Linux	Affected: 7.1 Unaffected: 0 , < 7.1 (semver) Unaffected: 7.1.5 , ≤ 7.1.* (semver) Unaffected: 7.2 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/ntfs/namei.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "b3d09502b80dfe0bab9090ca532710da389f6c7f",
              "status": "affected",
              "version": "af0db57d4293cc9fe6ce99fb5592dc2652228c9d",
              "versionType": "git"
            },
            {
              "lessThan": "eb94f5a41a193a425e09a63cb75dffd151d8f42e",
              "status": "affected",
              "version": "af0db57d4293cc9fe6ce99fb5592dc2652228c9d",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/ntfs/namei.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.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": "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: fix mrec_lock ABBA deadlock in rename\n\nntfs_file_fsync(), ntfs_dir_fsync() and __ntfs_write_inode() lock an\ninode\u0027s mrec_lock before taking the mrec_lock of its parent directory.\n\nntfs_rename() takes old_ni-\u003emrec_lock and old_dir_ni-\u003emrec_lock\nbefore taking new_ni-\u003emrec_lock for an existing target, or\nnew_dir_ni-\u003emrec_lock for a cross-directory rename.\nThis can deadlock when ntfs_file_fsync() or __ntfs_write_inode() holds\nthe target inode, or when ntfs_dir_fsync() holds a child target\ndirectory, while rename() holds the parent directory and waits for the\ntarget.\n\nFix this by locking the existing target inode before taking any parent\ndirectory mrec_lock. For cross-directory renames where the target parent\nis a descendant of the source parent, lock the target parent before the\nsource parent so the directory order matches the child-to-parent order used\nby ntfs_file_fsync(), ntfs_dir_fsync(), and __ntfs_write_inode()."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-17T05:09:55.301Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/b3d09502b80dfe0bab9090ca532710da389f6c7f"
        },
        {
          "url": "https://git.kernel.org/stable/c/eb94f5a41a193a425e09a63cb75dffd151d8f42e"
        }
      ],
      "title": "ntfs: fix mrec_lock ABBA deadlock in rename",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-72190",
    "datePublished": "2026-08-15T05:53:51.143Z",
    "dateReserved": "2026-08-09T03:40:39.911Z",
    "dateUpdated": "2026-08-17T05:09:55.301Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

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.

Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

Order JSON

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted