Vulnerability · Published May 27, 2026 · Assigned by Linux

CVE-2026-46013mm/memfd_luo: fix physical address conversion in put_folios cleanup

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 1% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.1%top 98.8% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official 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

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:14linux7.0.4-1DEBIAN-CVE-2026-46013
Ubuntu:26.04:LTSlinux7.0.0-27.27UBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-46013
Ubuntu:26.04:LTSlinux-aws7.0.0-1008.8UBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-46013
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-46013
Ubuntu:26.04:LTSlinux-azure7.0.0-1010.10UBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-46013
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-46013
Ubuntu:26.04:LTSlinux-azure-fde7.0.0-1009.9UBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-46013
Ubuntu:26.04:LTSlinux-gcp7.0.0-1007.7UBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-46013
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-46013
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-46013
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-46013
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-46013
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-28.28~24.04.1UBUNTU-CVE-2026-46013
Ubuntu:26.04:LTSlinux-ibm7.0.0-1009.9UBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-46013
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-46013
Ubuntu:26.04:LTSlinux-nvidia7.0.0-1013.13UBUNTU-CVE-2026-46013
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-46013
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-46013
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-46013
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-46013
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1008.8USN-8489-1
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1008.8UBUNTU-CVE-2026-46013
Ubuntu:26.04:LTSlinux-oracle7.0.0-1007.7UBUNTU-CVE-2026-46013
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-46013
Ubuntu:26.04:LTSlinux-raspi7.0.0-1014.14UBUNTU-CVE-2026-46013
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-46013
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-46013
Ubuntu:26.04:LTSlinux-realtime7.0.0-27.27.1UBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-46013
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-46013
Ubuntu:26.04:LTSlinux-riscv7.0.0-27.27.1UBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-46013
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-46013
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-46013

Affected products (as reported)

VendorProductVersions
Linux Linux b3749f174d686627f702234e64bad976dc432dbc – before bd0d6bde286a2b8e3ae7975b0dcc2d43875d5fc9b3749f174d686627f702234e64bad976dc432dbc – before 3538f90ab89aaf302782b4b073a0aae66904cd67
Linux Linux 6.19

References