Vulnerability · Published Apr 8, 2025 · Assigned by Linux

CVE-2025-22015mm/migrate: fix shmem xarray update during migration

High 7.8

In plain English

A high-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.2% (higher than 12% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.8High
Exploit odds (30 days)0.2%top 87.7% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: mm/migrate: fix shmem xarray update during migration A shmem folio can be either in page cache or in swap cache, but not at the same time. Namely, once it is in swap cache, folio->mapping should be NULL, and the folio is no longer in a shmem mapping. In __folio_migrate_mapping(), to determine the number of xarray entries to update, folio_test_swapbacked() is used, but that conflates shmem in page cache case and shmem in swap cache case. It leads to xarray multi-index entry corruption, since it turns a sibling entry to a normal entry during xas_store() (see [1] for a userspace reproduction). Fix it by only using folio_test_swapcache() to determine whether xarray is storing swap cache entries or not to choose the right number of xarray entries to update. [1] https://lore.kernel.org/linux-mm/Z8idPCkaJW1IChjT@casper.infradead.org/ Note: In __split_huge_page(), folio_test_anon() && folio_test_swapcache() is used to get swap_cache address space, but that ignores the shmem folio in swap cache case. It could lead to NULL pointer dereferencing when a in-swap-cache shmem folio is split at __xa_store(), since !folio_test_anon() is true and folio->mapping is NULL. But fortunately, its caller split_huge_page_to_list_to_order() bails out early with EBUSY when folio->mapping is NULL. So no need to take care of it here.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.133-1DEBIAN-CVE-2025-22015
Debian:13linux6.12.21-1DEBIAN-CVE-2025-22015
Debian:14linux6.12.21-1DEBIAN-CVE-2025-22015
Ubuntu:24.04:LTSlinux6.8.0-84.84UBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-aws6.8.0-1039.41UBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-aws-6.86.8.0-1039.41~22.04.1UBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-azure6.8.0-1038.44UBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-azure-6.116.11.0-1018.18~24.04.1UBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-azure-6.86.8.0-1036.42~22.04.1UBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-azure-nvidia6.8.0-1025.27UBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-gcp6.8.0-1040.42UBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-gcp-6.116.11.0-1016.16~24.04.1UBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-gcp-6.86.8.0-1040.42~22.04.1UBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-gke6.8.0-1036.40UBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-gkeop6.8.0-1023.25UBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-hwe-6.116.11.0-28.28~24.04.1UBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-hwe-6.86.8.0-85.85~22.04.1UBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-ibm6.8.0-1037.37UBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-ibm-6.86.8.0-1037.37~22.04.1UBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-intelno fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-lowlatency6.8.0-84.84.1UBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.116.11.0-1015.16~24.04.2UBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.86.8.0-84.84.1~22.04.1UBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-nvidia6.8.0-1039.42UBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-nvidia-6.116.11.0-1012.12UBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-nvidia-6.86.8.0-1039.42~22.04.1UBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-nvidia-lowlatency6.8.0-1039.42.1UBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-nvidia-tegra6.8.0-1010.10UBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-oem-6.116.11.0-1024.24UBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-oracle6.8.0-1037.38UBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-oracle-6.86.8.0-1037.38~22.04.1UBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-raspi6.8.0-1039.43UBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-riscv-6.86.8.0-84.84~22.04.1UBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2025-22015
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2025-22015
Ubuntu:24.04:LTSlinux-xilinx6.8.0-1018.19UBUNTU-CVE-2025-22015

Affected products (as reported)

VendorProductVersions
Linux Linux be72d197b2281e2ee3f28017fc9be1ab17e26d16 – before 49100c0b070e900f87c8fac3be9b9ef8a30fa67307550b1461d4d0499165e7d6f7718cfd0e440427 – before 29124ae980e2860f0eec7355949d3d3292ee81dafc346d0a70a13d52fe1c4bc49516d83a42cd7c4c – before c057ee03f751d6cecf7ee64f52f6545d94082aaafc346d0a70a13d52fe1c4bc49516d83a42cd7c4c – before 75cfb92eb63298d717b6b0118f91ba12c4fcfeb5fc346d0a70a13d52fe1c4bc49516d83a42cd7c4c – before 60cf233b585cdf1f3c5e52d1225606b86acd08b06.1.71 – before 6.1.1326.6.10 – before 6.6.85
Linux Linux 6.7

References