# CVE-2026-46013: linux: In the Linux kernel, the following vulnerability has been resolved:  mm/memfd_luo: fix physical address conversion in...

CVE-2026-46013 is fixed in linux on 1 platform by DEBIAN-CVE-2026-46013 (version 7.0.4-1), released May 27, 2026. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2026-46013
- Priority: Routine
- CVSS: 5.5 (medium)
- EPSS: 0.0011
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: May 27, 2026

## Description

In the Linux kernel, the following vulnerability has been resolved:  mm/memfd_luo: fix physical address conversion in put_folios cleanup  In memfd_luo_retrieve_folios()'s put_folios cleanup path:  1. kho_restore_folio() expects a phys_addr_t (physical address) but    receives a raw PFN (pfolio->pfn). This causes kho_restore_page() to    check the wrong physical address (pfn << PAGE_SHIFT instead of the    actual physical address).  2. This loop lacks the !pfolio->pfn check that exists in the main    retrieval loop and memfd_luo_discard_folios(), which could    incorrectly process sparse file holes where pfn=0.  Fix by converting PFN to physical address with PFN_PHYS() and adding the !pfolio->pfn check, matching the pattern used elsewhere in this file.  This issue was identified by the AI review. https://sashiko.dev/#/patchset/20260323110747.193569-1-duanchenghao@kylinos.cn

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 14 | 7.0.4-1 | [DEBIAN-CVE-2026-46013](https://patchblox.com/security/data/fix/linux/debian-cve-2026-46013.md) | May 27, 2026 |

---

Data as of 2026-11-08T06:59:42Z 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.