cbcvebase.
CVE-2025-22015
published 2025-04-08

CVE-2025-22015: 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…

PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.20%
9.8th percentile
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/[email protected]/ 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

27 ranges· showing 25
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.133-1 (bookworm)linux 6.1.133-1 (bookworm)
debianlinux-6.1< linux 6.1.133-1 (bookworm)linux 6.1.133-1 (bookworm)
linuxlinux
linuxlinux>= 07550b1461d4d0499165e7d6f7718cfd0e440427 < 29124ae980e2860f0eec7355949d3d3292ee81da29124ae980e2860f0eec7355949d3d3292ee81da
linuxlinux>= 6.1.71 < 6.1.1326.1.132
linuxlinux>= 6.6.10 < 6.6.856.6.85
linuxlinux>= be72d197b2281e2ee3f28017fc9be1ab17e26d16 < 49100c0b070e900f87c8fac3be9b9ef8a30fa67349100c0b070e900f87c8fac3be9b9ef8a30fa673
linuxlinux>= fc346d0a70a13d52fe1c4bc49516d83a42cd7c4c < c057ee03f751d6cecf7ee64f52f6545d94082aaac057ee03f751d6cecf7ee64f52f6545d94082aaa
linuxlinux>= fc346d0a70a13d52fe1c4bc49516d83a42cd7c4c < 75cfb92eb63298d717b6b0118f91ba12c4fcfeb575cfb92eb63298d717b6b0118f91ba12c4fcfeb5
linuxlinux>= fc346d0a70a13d52fe1c4bc49516d83a42cd7c4c < 60cf233b585cdf1f3c5e52d1225606b86acd08b060cf233b585cdf1f3c5e52d1225606b86acd08b0
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel>= 0 < 6.1.133-16.1.133-1
linuxlinux_kernel>= 0 < 6.12.21-16.12.21-1
linuxlinux_kernel>= 0 < 6.12.21-16.12.21-1
linuxlinux_kernel>= 0 < 6.8.0-84.846.8.0-84.84
linuxlinux_kernel>= 6.1.71 < 6.1.1326.1.132
linuxlinux_kernel>= 6.13 < 6.13.96.13.9

CVSS provenance

nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.9MEDIUM
vendor_ubuntu5.9MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.