GHSA-5QGV-47P9-J8PX

Vulnerability from github – Published: 2026-11-20 06:32 – Updated: 2026-11-20 06:32
VLAI
Details

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

mm/filemap: read mapping->a_ops->free_folio under i_lock

memory_failure() -> ... -> filemap_remove_folio() can read mapping->a_ops after the inode has been freed. Once the folio is deleted from the pagecache it no longer pins the mapping, so after i_lock is dropped e.g., a concurrent final iput() can evict and free the inode before filemap_free_folio() looks up mapping->a_ops->free_folio.

Most callers hold a reference on the inode, but not all.

Documentation/filesystems/vfs.rst explicitly states that ->free_folio() must not assume the original address_space mapping still exists.

Fix it by loading ->free_folio while i_lock is still held, similar to what folio_unmap_invalidate() does.

Inline filemap_free_folio() into its remaining caller such that delete_from_page_cache_batch() also just loads the callback before dropping the i_lock.

The bug was found by code inspection and has not been reproduced.

Fix generated by an LLM and sent by Josef Bacik in private.

[ david: get rid of filemap_free_folio() entirely; improve patch description ]

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-99732"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-11-20T06:18:10Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/filemap: read mapping-\u003ea_ops-\u003efree_folio under i_lock\n\nmemory_failure() -\u003e ... -\u003e filemap_remove_folio() can read mapping-\u003ea_ops\nafter the inode has been freed. Once the folio is deleted from the\npagecache it no longer pins the mapping, so after i_lock is dropped\ne.g., a concurrent final iput() can evict and free the inode before\nfilemap_free_folio() looks up mapping-\u003ea_ops-\u003efree_folio.\n\nMost callers hold a reference on the inode, but not all.\n\nDocumentation/filesystems/vfs.rst explicitly states that -\u003efree_folio()\nmust not assume the original address_space mapping still exists.\n\nFix it by loading -\u003efree_folio while i_lock is still held, similar to\nwhat folio_unmap_invalidate() does.\n\nInline filemap_free_folio() into its remaining caller such that\ndelete_from_page_cache_batch() also just loads the callback before\ndropping the i_lock.\n\nThe bug was found by code inspection and has not been reproduced.\n\nFix generated by an LLM and sent by Josef Bacik in private.\n\n[ david: get rid of filemap_free_folio() entirely; improve patch description ]",
  "id": "GHSA-5qgv-47p9-j8px",
  "modified": "2026-11-20T06:32:09Z",
  "published": "2026-11-20T06:32:09Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99732"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/842bfdb63ff2f9fcc3edc7ae6a33dfae3747a56e"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/dc24e273244e9d712257d5a6c20a32c7f5ca84e6"
    }
  ],
  "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
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.

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.