# CVE-2026-74591: linux: In the Linux kernel, the following vulnerability has been resolved: mm/filemap: __filemap_add_folio() restore index... CVE-2026-74591 is fixed in 20 products on 1 platform, first by DEBIAN-CVE-2026-74591, released September 4, 2026. It is not reported as exploited. Patch Radar priority: Urgent. - Web page: https://patchblox.com/security/cve/CVE-2026-74591 - Priority: Urgent - CVSS: 9.8 (critical) - EPSS: 0.0044 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: Aug 22, 2026 ## Description In the Linux kernel, the following vulnerability has been resolved: mm/filemap: __filemap_add_folio() restore index before retrying In __filemap_add_folio()'s split-a-conflict loop, xas_set_order() is applied repeatedly: each application modifies xas.xa_index, rounding it down according to the split_order attempted at that stage: and if all goes as intended, it eventually (or immediately) converges on an xas_try_split() to the required folio_order, with xas.xa_index now the same as index: then xas_store() puts the new folio into the xarray there. But if a new node was needed, and GFP_NOWAIT allocation did not get one, the lock is dropped, xas_nomem() used to allocate, and sequence retried. If (that part of) the xarray is unchanged when the lock is reacquired, no problem. But what if the conflict was meanwhile resolved by another thread (perhaps even doing the same thing, inserting a folio at that same index)? Isn't there a danger of now putting our folio into the xarray at an intermediate rounded-down index? With !folio_contains() bug to follow, when CONFIG_DEBUG_VM=y is checking for that. Fix this with an xas_set_order() to restore the original xas.xa_index at the bottom of the loop, so the retry does a full re-evaluation after reacquiring the lock, and cannot reach xas_store() with the wrong index. Production was suffering from rare SIGILLs and SIGSEGVs, executable text found a page away from where it belonged, !folio_contains() bug hit when debug enabled: symptoms not seen since this patch went in. ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | bpftool6.18 amzn 2023 | 1:6.18.48-107.148.amzn2023 | [ALAS2023-2026-3139](https://patchblox.com/security/data/fix/linux/alas2023-2026-3139.md) | Sep 28, 2026 | | Linux | bpftool6.18-debuginfo amzn 2023 | 1:6.18.48-107.148.amzn2023 | [ALAS2023-2026-3139](https://patchblox.com/security/data/fix/linux/alas2023-2026-3139.md) | Sep 28, 2026 | | Linux | kernel-livepatch-6.18.48-107.148 amzn 2023 | 1:1.0-0.amzn2023 | [ALAS2023-2026-3139](https://patchblox.com/security/data/fix/linux/alas2023-2026-3139.md) | Sep 28, 2026 | | Linux | kernel6.18 amzn 2023 | 1:6.18.48-107.148.amzn2023 | [ALAS2023-2026-3139](https://patchblox.com/security/data/fix/linux/alas2023-2026-3139.md) | Sep 28, 2026 | | Linux | kernel6.18-debuginfo amzn 2023 | 1:6.18.48-107.148.amzn2023 | [ALAS2023-2026-3139](https://patchblox.com/security/data/fix/linux/alas2023-2026-3139.md) | Sep 28, 2026 | | Linux | kernel6.18-debuginfo-common-aarch64 amzn 2023 | 1:6.18.48-107.148.amzn2023 | [ALAS2023-2026-3139](https://patchblox.com/security/data/fix/linux/alas2023-2026-3139.md) | Sep 28, 2026 | | Linux | kernel6.18-debuginfo-common-x86_64 amzn 2023 | 1:6.18.48-107.148.amzn2023 | [ALAS2023-2026-3139](https://patchblox.com/security/data/fix/linux/alas2023-2026-3139.md) | Sep 28, 2026 | | Linux | kernel6.18-devel amzn 2023 | 1:6.18.48-107.148.amzn2023 | [ALAS2023-2026-3139](https://patchblox.com/security/data/fix/linux/alas2023-2026-3139.md) | Sep 28, 2026 | | Linux | kernel6.18-headers amzn 2023 | 1:6.18.48-107.148.amzn2023 | [ALAS2023-2026-3139](https://patchblox.com/security/data/fix/linux/alas2023-2026-3139.md) | Sep 28, 2026 | | Linux | kernel6.18-modules-extra amzn 2023 | 1:6.18.48-107.148.amzn2023 | [ALAS2023-2026-3139](https://patchblox.com/security/data/fix/linux/alas2023-2026-3139.md) | Sep 28, 2026 | | Linux | kernel6.18-modules-extra-common amzn 2023 | 1:6.18.48-107.148.amzn2023 | [ALAS2023-2026-3139](https://patchblox.com/security/data/fix/linux/alas2023-2026-3139.md) | Sep 28, 2026 | | Linux | kernel6.18-tools amzn 2023 | 1:6.18.48-107.148.amzn2023 | [ALAS2023-2026-3139](https://patchblox.com/security/data/fix/linux/alas2023-2026-3139.md) | Sep 28, 2026 | | Linux | kernel6.18-tools-debuginfo amzn 2023 | 1:6.18.48-107.148.amzn2023 | [ALAS2023-2026-3139](https://patchblox.com/security/data/fix/linux/alas2023-2026-3139.md) | Sep 28, 2026 | | Linux | kernel6.18-tools-devel amzn 2023 | 1:6.18.48-107.148.amzn2023 | [ALAS2023-2026-3139](https://patchblox.com/security/data/fix/linux/alas2023-2026-3139.md) | Sep 28, 2026 | | Linux | linux Debian 14 | 7.1.9-1 | [DEBIAN-CVE-2026-74591](https://patchblox.com/security/data/fix/linux/debian-cve-2026-74591.md) | Sep 4, 2026 | | Linux | microvm-kernel6.18 amzn 2023 | 1:6.18.48-107.148.amzn2023 | [ALAS2023-2026-3139](https://patchblox.com/security/data/fix/linux/alas2023-2026-3139.md) | Sep 28, 2026 | | Linux | perf6.18 amzn 2023 | 1:6.18.48-107.148.amzn2023 | [ALAS2023-2026-3139](https://patchblox.com/security/data/fix/linux/alas2023-2026-3139.md) | Sep 28, 2026 | | Linux | perf6.18-debuginfo amzn 2023 | 1:6.18.48-107.148.amzn2023 | [ALAS2023-2026-3139](https://patchblox.com/security/data/fix/linux/alas2023-2026-3139.md) | Sep 28, 2026 | | Linux | python3-perf6.18 amzn 2023 | 1:6.18.48-107.148.amzn2023 | [ALAS2023-2026-3139](https://patchblox.com/security/data/fix/linux/alas2023-2026-3139.md) | Sep 28, 2026 | | Linux | python3-perf6.18-debuginfo amzn 2023 | 1:6.18.48-107.148.amzn2023 | [ALAS2023-2026-3139](https://patchblox.com/security/data/fix/linux/alas2023-2026-3139.md) | Sep 28, 2026 | --- Data as of 2026-11-08T19:12:23Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.