PatchSiren cyber security CVE debrief
CVE-2026-46013 Linux CVE debrief
A vulnerability in the Linux kernel's memfd_luo subsystem has been resolved. The issue involved incorrect physical address conversion in the put_folios cleanup path of memfd_luo_retrieve_folios(). Specifically, kho_restore_folio() received a raw PFN instead of a proper phys_addr_t, causing kho_restore_page() to check the wrong physical address. Additionally, the cleanup loop lacked a !pfolio->pfn check present in other code paths, potentially causing incorrect processing of sparse file holes where pfn=0. The fix converts PFN to physical address using PFN_PHYS() and adds the missing pfn validation check. This vulnerability was identified through AI review.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- MEDIUM 5.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-05-27
- Original CVE updated
- 2026-06-16
- Advisory published
- 2026-05-27
- Advisory updated
- 2026-06-16
Who should care
Linux kernel maintainers, system administrators running Linux systems with memfd_luo support, security teams tracking kernel memory management vulnerabilities, and organizations using AI-assisted code review processes
Technical summary
CVE-2026-46013 is a resolved vulnerability in the Linux kernel's memfd_luo (memory file descriptor with large/unique objects) subsystem. The bug occurred in memfd_luo_retrieve_folios()'s put_folios cleanup path where kho_restore_folio() incorrectly received a raw page frame number (PFN) instead of a converted physical address. This caused kho_restore_page() to validate the wrong address (pfn << PAGE_SHIFT rather than the actual physical address). Additionally, the cleanup path was missing a !pfolio->pfn check that exists in the main retrieval loop and memfd_luo_discard_folios(), which could lead to incorrect processing of sparse file holes where pfn=0. The resolution applies PFN_PHYS() macro for proper address conversion and adds the missing pfn validation, aligning with patterns used elsewhere in the file. The vulnerability was discovered through AI-assisted code review.
Defensive priority
medium
Recommended defensive actions
- Review kernel version and apply stable kernel updates containing the fix commits
- Verify memfd_luo functionality is not required for critical workloads if temporary mitigation is needed
- Monitor kernel changelogs for memfd_luo-related fixes in your distribution's kernel package
- Consider disabling memfd_luo if not required and if your kernel configuration permits
- Audit systems for any unusual memory management behavior that could indicate exploitation attempts
Evidence notes
The vulnerability description indicates this was identified by AI review and has been resolved in the Linux kernel. The fix involves proper PFN-to-physical-address conversion and validation checks matching patterns used elsewhere in the memfd_luo implementation.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-46013 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-46013
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-46013 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-46013
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/3538f90ab89aaf302782b4b073a0aae66904cd67
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/bd0d6bde286a2b8e3ae7975b0dcc2d43875d5fc9
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.