Vulnerability-Lookup

GHSA-HW8W-QHG7-G497

Vulnerability from github – Published: 2026-06-24 18:32 – Updated: 2026-07-15 15:32

Details

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

fs/ntfs3: prevent uninitialized lcn caused by zero len

syzbot reported a uninit-value in ntfs_iomap_begin [1].

Since runs was not touched yet, run_lookup_entry() immediately fails and returns false, which makes the value of "len" 0. Simultaneously, the new value and err value are also 0, causing the logic in attr_data_get_block_locked() to jump directly to ok, ultimately resulting in lcn being triggered before it is set [1].

In ntfs_iomap_begin(), the check for a 0 value in clen is moved forward to before updating lcn to avoid this [1].

[1] BUG: KMSAN: uninit-value in ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825 ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825 iomap_iter+0x9b7/0x1540 fs/iomap/iter.c:110

Local variable lcn created at: ntfs_iomap_begin+0x15d/0x1460 fs/ntfs3/inode.c:786

Severity

5.5 (Medium)


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

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-53029"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-908"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-06-24T17:17:14Z",
    "severity": "MODERATE"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: prevent uninitialized lcn caused by zero len\n\nsyzbot reported a uninit-value in ntfs_iomap_begin [1].\n\nSince runs was not touched yet, run_lookup_entry() immediately fails\nand returns false, which makes the value of \"*len\" 0.\nSimultaneously, the new value and err value are also 0, causing the\nlogic in attr_data_get_block_locked() to jump directly to ok, ultimately\nresulting in *lcn being triggered before it is set [1].\n\nIn ntfs_iomap_begin(), the check for a 0 value in clen is moved forward\nto before updating lcn to avoid this [1].\n\n[1]\nBUG: KMSAN: uninit-value in ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825\n ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825\n iomap_iter+0x9b7/0x1540 fs/iomap/iter.c:110\n\nLocal variable lcn created at:\n ntfs_iomap_begin+0x15d/0x1460 fs/ntfs3/inode.c:786",
  "id": "GHSA-hw8w-qhg7-g497",
  "modified": "2026-07-15T15:32:45Z",
  "published": "2026-06-24T18:32:44Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-53029"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/485f750cac3d8bdf5552a0e3d79ce5e3a03ece49"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/e98266e823a1fa06fe6499df61aeaac2fd6f7a49"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}

CVE-2026-53029 (GCVE-0-2026-53029)

Vulnerability from cvelistv5 – Published: 2026-06-24 16:29 – Updated: 2026-06-24 16:29

Title

fs/ntfs3: prevent uninitialized lcn caused by zero len

Summary

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: prevent uninitialized lcn caused by zero len syzbot reported a uninit-value in ntfs_iomap_begin [1]. Since runs was not touched yet, run_lookup_entry() immediately fails and returns false, which makes the value of "*len" 0. Simultaneously, the new value and err value are also 0, causing the logic in attr_data_get_block_locked() to jump directly to ok, ultimately resulting in *lcn being triggered before it is set [1]. In ntfs_iomap_begin(), the check for a 0 value in clen is moved forward to before updating lcn to avoid this [1]. [1] BUG: KMSAN: uninit-value in ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825 ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825 iomap_iter+0x9b7/0x1540 fs/iomap/iter.c:110 Local variable lcn created at: ntfs_iomap_begin+0x15d/0x1460 fs/ntfs3/inode.c:786

Severity

No CVSS data available.

Assigner

Linux mitre root

References

2 references

URL	Tags
https://git.kernel.org/stable/c/485f750cac3d8bdf5…
https://git.kernel.org/stable/c/e98266e823a1fa06f…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 10d7c95af043b45a85dc738c3271bf760ff3577e , < 485f750cac3d8bdf5552a0e3d79ce5e3a03ece49 (git) Affected: 10d7c95af043b45a85dc738c3271bf760ff3577e , < e98266e823a1fa06fe6499df61aeaac2fd6f7a49 (git)
Linux	Linux	Affected: 7.0 Unaffected: 0 , < 7.0 (semver) Unaffected: 7.0.10 , ≤ 7.0.* (semver) Unaffected: 7.1 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/ntfs3/inode.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "485f750cac3d8bdf5552a0e3d79ce5e3a03ece49",
              "status": "affected",
              "version": "10d7c95af043b45a85dc738c3271bf760ff3577e",
              "versionType": "git"
            },
            {
              "lessThan": "e98266e823a1fa06fe6499df61aeaac2fd6f7a49",
              "status": "affected",
              "version": "10d7c95af043b45a85dc738c3271bf760ff3577e",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/ntfs3/inode.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "7.0"
            },
            {
              "lessThan": "7.0",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.0.*",
              "status": "unaffected",
              "version": "7.0.10",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0.10",
                  "versionStartIncluding": "7.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1",
                  "versionStartIncluding": "7.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: prevent uninitialized lcn caused by zero len\n\nsyzbot reported a uninit-value in ntfs_iomap_begin [1].\n\nSince runs was not touched yet, run_lookup_entry() immediately fails\nand returns false, which makes the value of \"*len\" 0.\nSimultaneously, the new value and err value are also 0, causing the\nlogic in attr_data_get_block_locked() to jump directly to ok, ultimately\nresulting in *lcn being triggered before it is set [1].\n\nIn ntfs_iomap_begin(), the check for a 0 value in clen is moved forward\nto before updating lcn to avoid this [1].\n\n[1]\nBUG: KMSAN: uninit-value in ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825\n ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825\n iomap_iter+0x9b7/0x1540 fs/iomap/iter.c:110\n\nLocal variable lcn created at:\n ntfs_iomap_begin+0x15d/0x1460 fs/ntfs3/inode.c:786"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-06-24T16:29:37.361Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/485f750cac3d8bdf5552a0e3d79ce5e3a03ece49"
        },
        {
          "url": "https://git.kernel.org/stable/c/e98266e823a1fa06fe6499df61aeaac2fd6f7a49"
        }
      ],
      "title": "fs/ntfs3: prevent uninitialized lcn caused by zero len",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-53029",
    "datePublished": "2026-06-24T16:29:37.361Z",
    "dateReserved": "2026-06-09T07:44:35.380Z",
    "dateUpdated": "2026-06-24T16:29:37.361Z",
    "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.

Detection rules are retrieved from Rulezet.

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.