{
  "affected": [
    {
      "ranges": [
        {
          "events": [
            {
              "introduced": "59c66c5f8c4fb823240d70553c1686ce4e4dd331"
            },
            {
              "fixed": "842bfdb63ff2f9fcc3edc7ae6a33dfae3747a56e"
            },
            {
              "fixed": "dc24e273244e9d712257d5a6c20a32c7f5ca84e6"
            }
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "type": "GIT"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Linux",
        "name": "Kernel"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "4.15.0"
            },
            {
              "fixed": "7.3.5"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99732.json"
  },
  "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": "CVE-2026-99732",
  "modified": "2026-11-20T06:45:34.728093062Z",
  "published": "2026-11-20T05:51:06.788Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/842bfdb63ff2f9fcc3edc7ae6a33dfae3747a56e"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/dc24e273244e9d712257d5a6c20a32c7f5ca84e6"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99732.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99732"
    }
  ],
  "schema_version": "1.9.2",
  "summary": "mm/filemap: read mapping-\u003ea_ops-\u003efree_folio under i_lock"
}