Vulnerability-Lookup

GHSA-WHJW-7H99-RMG2

Vulnerability from github – Published: 2026-09-11 21:31 – Updated: 2026-09-13 09:32

Details

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

ntfs: verify run length exceeding volume boundary

The mapping pairs decoder validates that the starting LCN is within the volume but does not check if the run extends beyond the volume boundary.

A malformed NTFS image with a crafted mapping pairs array could cause the kernel to access memory beyond the volume boundary, potentially leading to memory corruption and privilege escalation.

Add validation to ensure lcn + length stays within nr_clusters.

Severity

9.8 (Critical)


                  
                    CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-89610"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-11T20:19:46Z",
    "severity": "CRITICAL"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nntfs: verify run length exceeding volume boundary\n\nThe mapping pairs decoder validates that the starting LCN is within the\nvolume but does not check if the run extends beyond the volume boundary.\n\nA malformed NTFS image with a crafted mapping pairs array could cause\nthe kernel to access memory beyond the volume boundary, potentially leading\nto memory corruption and privilege escalation.\n\nAdd validation to ensure lcn + length stays within nr_clusters.",
  "id": "GHSA-whjw-7h99-rmg2",
  "modified": "2026-09-13T09:32:20Z",
  "published": "2026-09-11T21:31:33Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89610"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/6e844d4b82434a781b80d02145fd1b17cf90e3c3"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/fea9e4488f384c0ef1c0e3d96b565127c1b98447"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

CVE-2026-89610 (GCVE-0-2026-89610)

Vulnerability from cvelistv5 – Published: 2026-09-11 19:45 – Updated: 2026-10-19 08:49

Title

ntfs: verify run length exceeding volume boundary

Summary

In the Linux kernel, the following vulnerability has been resolved: ntfs: verify run length exceeding volume boundary The mapping pairs decoder validates that the starting LCN is within the volume but does not check if the run extends beyond the volume boundary. A malformed NTFS image with a crafted mapping pairs array could cause the kernel to access memory beyond the volume boundary, potentially leading to memory corruption and privilege escalation. Add validation to ensure lcn + length stays within nr_clusters.

Severity

9.8 (Critical)


                        
                          CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Assigner

Linux CNA under the mitre root

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

References

2 references

URL	Tags
https://git.kernel.org/stable/c/6e844d4b82434a781…
https://git.kernel.org/stable/c/fea9e4488f384c0ef…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < 6e844d4b82434a781b80d02145fd1b17cf90e3c3 (git) Affected: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 , < fea9e4488f384c0ef1c0e3d96b565127c1b98447 (git) Affected: 0 , < 7.2.4 (semver)
Linux	Linux	Unaffected: 7.2.4 , ≤ 7.2.* (semver) Unaffected: 7.3 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/ntfs/runlist.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "6e844d4b82434a781b80d02145fd1b17cf90e3c3",
              "status": "affected",
              "version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
              "versionType": "git"
            },
            {
              "lessThan": "fea9e4488f384c0ef1c0e3d96b565127c1b98447",
              "status": "affected",
              "version": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2",
              "versionType": "git"
            },
            {
              "lessThan": "7.2.4",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/ntfs/runlist.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.4",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.4",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nntfs: verify run length exceeding volume boundary\n\nThe mapping pairs decoder validates that the starting LCN is within the\nvolume but does not check if the run extends beyond the volume boundary.\n\nA malformed NTFS image with a crafted mapping pairs array could cause\nthe kernel to access memory beyond the volume boundary, potentially leading\nto memory corruption and privilege escalation.\n\nAdd validation to ensure lcn + length stays within nr_clusters."
        }
      ],
      "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 - fs/ntfs registers ntfs_export_ops, so nfsd/ksmbd VFS reads and writes on an exported NTFS volume reach ntfs_map_runlist()-\u003entfs_mapping_pairs_decompress() and later use the over-long run via iomap and bitmap updates without local shell access.\nAC:L - The attacker fully controls on-disk mapping pairs and can set a start LCN below nr_clusters with a length that extends past the volume or overflows s64; decompression and subsequent use of that run are deterministic with no race or victim-specific layout.\nPR:N - Triggering the decoder needs only permission to cause server-side parsing of mounted NTFS metadata (guest/anonymous SMB or a permissive NFS export, or an unprivileged open/read on an already-mounted volume), not init-namespace root or CAP_SYS_ADMIN at trigger time.\nUI:N - After the crafted volume is mounted and exported, ordinary remote or local read/write/unlink operations decompress the poisoned mapping pairs and exercise the over-long run; no extra victim mount dialog, USB insertion, or confirmation is required during the attack.\nS:U - Heap corruption of vol-\u003elcn_empty_bits_per_page and misdirected block I/O remain in the host kernel/OS security domain and do not cross a VM, container, or IOMMU boundary to another authority.\nC:H - Over-long runs make ntfs_rl_vcn_to_lcn() return LCNs past nr_clusters, so iomap reads can disclose out-of-volume data, and ntfs_set_lcn_empty_bits() indexes lcn_empty_bits_per_page (sized only from nr_clusters), enabling kernel heap disclosure.\nI:H - The same run drives iomap writes past the volume and ntfs_bitmap_set_bits_in_run()/ntfs_set_lcn_empty_bits() past the allocated lcn_empty_bits_per_page array, a kernel heap OOB write and misdirected disk-write primitive consistent with the fix\u0027s memory-corruption and privilege-escalation impact.\nA:H - Out-of-bounds bitmap/heap access, I/O past the block device, and huge-length bitmap walks can oops, panic, or hang the kernel, so even failed exploitation denies service to the host or exported filesystem."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-19T08:49:42.613Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/6e844d4b82434a781b80d02145fd1b17cf90e3c3"
        },
        {
          "url": "https://git.kernel.org/stable/c/fea9e4488f384c0ef1c0e3d96b565127c1b98447"
        }
      ],
      "title": "ntfs: verify run length exceeding volume boundary",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-89610",
    "datePublished": "2026-09-11T19:45:11.864Z",
    "dateReserved": "2026-09-11T19:38:34.734Z",
    "dateUpdated": "2026-10-19T08:49:42.613Z",
    "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

How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

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