{
  "id": "CVE-2026-74591",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-74591",
  "published_at": "2026-08-22T15:31:42.661Z",
  "title": "mm/filemap: __filemap_add_folio() restore index before retrying",
  "vendor": "Linux",
  "product": "Linux",
  "cvss": {
    "score": 9.8,
    "source": "cna",
    "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/filemap: __filemap_add_folio() restore index before retrying\n\nIn __filemap_add_folio()'s split-a-conflict loop, xas_set_order() is\napplied repeatedly: each application modifies xas.xa_index, rounding it\ndown according to the split_order attempted at that stage: and if all goes\nas intended, it eventually (or immediately) converges on an\nxas_try_split() to the required folio_order, with xas.xa_index now the\nsame as index: then xas_store() puts the new folio into the xarray there.\n\nBut if a new node was needed, and GFP_NOWAIT allocation did not get one,\nthe lock is dropped, xas_nomem() used to allocate, and sequence retried. \nIf (that part of) the xarray is unchanged when the lock is reacquired, no\nproblem.  But what if the conflict was meanwhile resolved by another\nthread (perhaps even doing the same thing, inserting a folio at that same\nindex)?  Isn't there a danger of now putting our folio into the xarray at\nan intermediate rounded-down index?  With !folio_contains() bug to follow,\nwhen CONFIG_DEBUG_VM=y is checking for that.\n\nFix this with an xas_set_order() to restore the original xas.xa_index at\nthe bottom of the loop, so the retry does a full re-evaluation after\nreacquiring the lock, and cannot reach xas_store() with the wrong index.\n\nProduction was suffering from rare SIGILLs and SIGSEGVs, executable text\nfound a page away from where it belonged, !folio_contains() bug hit when\ndebug enabled: symptoms not seen since this patch went in.",
  "cvss_by_source": {
    "cna": 9.8
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "\u003e= 200a89c159a7a416115e6e309183c82183bf98aa, \u003c 4917e3ebcab50f0265e8ca01c8567de4c4a47511",
          "\u003e= 200a89c159a7a416115e6e309183c82183bf98aa, \u003c 267ecd2eb7759c26f1a026eb0a5b231071534c9c",
          "\u003e= 200a89c159a7a416115e6e309183c82183bf98aa, \u003c 86da3f7e1e609e1e8bfbab198af68467c5a015a5"
        ],
        "fixed_in": [
          "4917e3ebcab50f0265e8ca01c8567de4c4a47511",
          "267ecd2eb7759c26f1a026eb0a5b231071534c9c",
          "86da3f7e1e609e1e8bfbab198af68467c5a015a5"
        ]
      },
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "6.15"
        ],
        "fixed_in": [
          "0",
          "6.18.45",
          "7.1.9",
          "7.2"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Linux to 4917e3ebcab50f0265e8ca01c8567de4c4a47511 or 267ecd2eb7759c26f1a026eb0a5b231071534c9c or 86da3f7e1e609e1e8bfbab198af68467c5a015a5 or later.",
      "Upgrade Linux to 0 or 6.18.45 or 7.1.9 or 7.2 or later."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
