CVE-2026-74591

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.

• https://git.kernel.org/stable/c/267ecd2eb7759c26f1a026eb0a5b231071534c9c
• https://git.kernel.org/stable/c/4917e3ebcab50f0265e8ca01c8567de4c4a47511
• https://git.kernel.org/stable/c/86da3f7e1e609e1e8bfbab198af68467c5a015a5

Published

Aug 22, 2026

Last Modified

Oct 14, 2026

Status

Received

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-74586In the Linux kernel, the following vulnerability has been re…9.8
• CVE-2026-74587In the Linux kernel, the following vulnerability has been re…9.8
• CVE-2026-74588In the Linux kernel, the following vulnerability has been re…9.8
• CVE-2026-74589In the Linux kernel, the following vulnerability has been re…8.4
• CVE-2026-7459The Simple History – Track, Log, and Audit WordPress Changes…7.5
• CVE-2026-74590In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-74592In the Linux kernel, the following vulnerability has been re…8.1
• CVE-2026-74593In the Linux kernel, the following vulnerability has been re…
• CVE-2026-74594In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-74595In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-74596In the Linux kernel, the following vulnerability has been re…
• CVE-2026-74597In the Linux kernel, the following vulnerability has been re…9.8