CVE-2025-40272
Description
In the Linux kernel, the following vulnerability has been resolved:
mm/secretmem: fix use-after-free race in fault handler
When a page fault occurs in a secret memory file created with memfd_secret(2), the kernel will allocate a new folio for it, mark the underlying page as not-present in the direct map, and add it to the file mapping.
If two tasks cause a fault in the same page concurrently, both could end up allocating a folio and removing the page from the direct map, but only one would succeed in adding the folio to the file mapping. The task that failed undoes the effects of its attempt by (a) freeing the folio again and (b) putting the page back into the direct map. However, by doing these two operations in this order, the page becomes available to the allocator again before it is placed back in the direct mapping.
If another task attempts to allocate the page between (a) and (b), and the kernel tries to access it via the direct map, it would result in a supervisor not-present page fault.
Fix the ordering to restore the direct map before the folio is freed.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A use-after-free race condition in the Linux kernel's secretmem fault handler can lead to a crash.
Vulnerability
A race condition exists in the Linux kernel's mm/secretmem fault handler. When a page fault occurs in a secret memory file created with memfd_secret(2), the kernel allocates a new folio, removes the underlying page from the direct map, and adds the folio to the file mapping. If two tasks trigger a fault on the same page concurrently, both may allocate a folio and attempt the removal, but only one succeeds in adding the folio. The failing task frees its folio before restoring the direct map, creating a window where the freed page is available to the allocator but still absent from the direct map.
Exploitation
An attacker with local access and the ability to trigger concurrent page faults on the same secret memory page can exploit this race. No special privileges beyond being able to create and access secret memory files via memfd_secret(2) are required. The vulnerability is triggered during normal memory management operations, making it potentially reachable through unprivileged userspace code.
Impact
During the window between freeing the folio and restoring the direct map, any kernel access to the page via the direct map will cause a supervisor not-present page fault, leading to a denial of service (system crash). The issue is a use-after-free that can result in memory corruption and system instability.
Mitigation
The fix reorders the operations so that the direct map is restored before the folio is freed [1][2][3]. Patched versions are available via stable kernel updates. Systems unable to apply the patch should mitigate by restricting access to secret memory functionality or using kernel protections like KASLR and SMAP to reduce exploitability.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
6bb1c19636aed1e4643d6628e42d486d35a4152f2d5cf33de4444767e625d6f86d0534fddVulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
6- git.kernel.org/stable/c/1e4643d6628edf9c0047b1f8f5bc574665025acbnvd
- git.kernel.org/stable/c/42d486d35a4143cc37fc72ee66edc99d942dd367nvd
- git.kernel.org/stable/c/4444767e625da46009fc94a453fd1967b80ba047nvd
- git.kernel.org/stable/c/52f2d5cf33de9a8f5e72bbb0ed38282ae0bc4649nvd
- git.kernel.org/stable/c/6f86d0534fddfbd08687fa0f01479d4226bc3c3dnvd
- git.kernel.org/stable/c/bb1c19636aedae39360e6fdbcaef4f2bcff25785nvd
News mentions
0No linked articles in our index yet.