GHSA-PCHJ-J532-7CM6

Vulnerability from github – Published: 2026-10-28 12:31 – Updated: 2026-10-28 12:31
VLAI
Details

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

ntfs: take invalidate_lock in ntfs_setattr_size()

ntfs_setattr_size() updates i_size and resizes the on-disk attribute without holding mapping->invalidate_lock. Page faults take the lock shared, so a fault racing the resize can resolve a VCN against the transient runlist state of ntfs_non_resident_attr_expand() and fail with a spurious SIGBUS, and can interleave with the size-change epilogue (truncate_pagecache(), i_size_write(), pagecache_isize_extended()).

Take invalidate_lock exclusively around the whole resize after inode_dio_wait(), matching the fallocate path and other filesystems such as xfs, which wraps truncate in its mmaplock (= invalidate_lock).

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-99102"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-10-28T11:17:29Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nntfs: take invalidate_lock in ntfs_setattr_size()\n\nntfs_setattr_size() updates i_size and resizes the on-disk attribute\nwithout holding mapping-\u003einvalidate_lock.  Page faults take the lock\nshared, so a fault racing the resize can resolve a VCN against the\ntransient runlist state of ntfs_non_resident_attr_expand() and fail\nwith a spurious SIGBUS, and can interleave with the size-change\nepilogue (truncate_pagecache(), i_size_write(),\npagecache_isize_extended()).\n\nTake invalidate_lock exclusively around the whole resize after\ninode_dio_wait(), matching the fallocate path and other filesystems\nsuch as xfs, which wraps truncate in its mmaplock (= invalidate_lock).",
  "id": "GHSA-pchj-j532-7cm6",
  "modified": "2026-10-28T12:31:01Z",
  "published": "2026-10-28T12:31:01Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99102"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/9cc5761b8f28f9cef72061094eb5e37e2cd44d97"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/f0b0738ba95731eeafd11352c74f8b48951f67dc"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    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.