{ "dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": { "cveId": "CVE-2025-22015", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2024-12-29T08:45:45.806Z", "datePublished": "2025-04-08T08:18:05.287Z", "dateUpdated": "2026-08-05T11:56:00.432Z" }, "containers": { "cna": { "providerMetadata": { "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-08-05T11:56:00.432Z" }, "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/migrate: fix shmem xarray update during migration\n\nA shmem folio can be either in page cache or in swap cache, but not at the\nsame time. Namely, once it is in swap cache, folio->mapping should be\nNULL, and the folio is no longer in a shmem mapping.\n\nIn __folio_migrate_mapping(), to determine the number of xarray entries to\nupdate, folio_test_swapbacked() is used, but that conflates shmem in page\ncache case and shmem in swap cache case. It leads to xarray multi-index\nentry corruption, since it turns a sibling entry to a normal entry during\nxas_store() (see [1] for a userspace reproduction). Fix it by only using\nfolio_test_swapcache() to determine whether xarray is storing swap cache\nentries or not to choose the right number of xarray entries to update.\n\n[1] https://lore.kernel.org/linux-mm/Z8idPCkaJW1IChjT@casper.infradead.org/\n\nNote:\nIn __split_huge_page(), folio_test_anon() && folio_test_swapcache() is\nused to get swap_cache address space, but that ignores the shmem folio in\nswap cache case. It could lead to NULL pointer dereferencing when a\nin-swap-cache shmem folio is split at __xa_store(), since\n!folio_test_anon() is true and folio->mapping is NULL. But fortunately,\nits caller split_huge_page_to_list_to_order() bails out early with EBUSY\nwhen folio->mapping is NULL. So no need to take care of it here." } ], "metrics": [ { "cvssV3_1": { "version": "3.1", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "baseScore": 7.8, "baseSeverity": "HIGH" }, "scenarios": [ { "lang": "en", "value": "AV:L - The vulnerability is reached entirely through local syscalls — mounting tmpfs with huge=always, populating a large shmem folio, then mbind(MPOL_MF_MOVE)/move_pages()/madvise(MADV_PAGEOUT). There is no network-facing path into mm/migrate.c.\nAC:L - The corruption is deterministic, not a race: once a large shmem page-cache folio is migrated, folio_test_swapbacked() unconditionally selects the wrong entry count and the sibling entries are destroyed every time. The attacker creates all preconditions (the huge tmpfs mount, the folio, the migration, and the subsequent swapout) with no dependence on external state.\nPR:L - An ordinary unprivileged user suffices — tmpfs is FS_USERNS_MOUNT and its huge= option has no capability check (mm/shmem.c:4475), so a user namespace supplies large shmem folios, and migrating one's own pages requires no capability (only MPOL_MF_MOVE_ALL checks CAP_SYS_NICE). No root or real CAP_* in the init namespace is needed.\nUI:N - The attacking process performs every step itself — mount, allocate, migrate, swap out, and re-access. No victim action or cooperating process is involved.\nS:U - The corrupted xarray, the freed folio, and the resulting memory access all live within the kernel's own security authority. No VM, IOMMU, or sandbox boundary is crossed.\nC:H - After swapout frees the folio, nr-1 dangling pointers remain in the shmem page cache; once the page is reallocated the attacker reads it back through their own tmpfs file via read() or mmap, disclosing memory now owned by other processes, slab, or page tables.\nI:H - The same dangling page-cache entries are writable — write()/mmap on the tmpfs file modifies a page the allocator has handed to another owner, giving an arbitrary kernel-memory write primitive suitable for privilege escalation.\nA:H - filemap_get_entry() loops forever under rcu_read_lock() when folio_try_get() keeps failing on the zero-refcount folio, producing a soft lockup; BUG_ON(error) in shmem_delete_from_page_cache() and the VM_BUG_ON_FOLIO checks give additional panic/oops paths." } ] } ], "affected": [ { "product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": [ "mm/migrate.c" ], "versions": [ { "version": "be72d197b2281e2ee3f28017fc9be1ab17e26d16", "lessThan": "49100c0b070e900f87c8fac3be9b9ef8a30fa673", "status": "affected", "versionType": "git" }, { "version": "07550b1461d4d0499165e7d6f7718cfd0e440427", "lessThan": "29124ae980e2860f0eec7355949d3d3292ee81da", "status": "affected", "versionType": "git" }, { "version": "fc346d0a70a13d52fe1c4bc49516d83a42cd7c4c", "lessThan": "c057ee03f751d6cecf7ee64f52f6545d94082aaa", "status": "affected", "versionType": "git" }, { "version": "fc346d0a70a13d52fe1c4bc49516d83a42cd7c4c", "lessThan": "75cfb92eb63298d717b6b0118f91ba12c4fcfeb5", "status": "affected", "versionType": "git" }, { "version": "fc346d0a70a13d52fe1c4bc49516d83a42cd7c4c", "lessThan": "60cf233b585cdf1f3c5e52d1225606b86acd08b0", "status": "affected", "versionType": "git" }, { "version": "6.1.71", "lessThan": "6.1.132", "status": "affected", "versionType": "semver" }, { "version": "6.6.10", "lessThan": "6.6.85", "status": "affected", "versionType": "semver" } ] }, { "product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": [ "mm/migrate.c" ], "versions": [ { "version": "6.7", "status": "affected" }, { "version": "0", "lessThan": "6.7", "status": "unaffected", "versionType": "semver" }, { "version": "6.1.132", "lessThanOrEqual": "6.1.*", "status": "unaffected", "versionType": "semver" }, { "version": "6.6.85", "lessThanOrEqual": "6.6.*", "status": "unaffected", "versionType": "semver" }, { "version": "6.12.21", "lessThanOrEqual": "6.12.*", "status": "unaffected", "versionType": "semver" }, { "version": "6.13.9", "lessThanOrEqual": "6.13.*", "status": "unaffected", "versionType": "semver" }, { "version": "6.14", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix" } ] } ], "cpeApplicability": [ { "nodes": [ { "operator": "OR", "negate": false, "cpeMatch": [ { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.1.71", "versionEndExcluding": "6.1.132" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.6.10", "versionEndExcluding": "6.6.85" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.7", "versionEndExcluding": "6.12.21" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.7", "versionEndExcluding": "6.13.9" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.7", "versionEndExcluding": "6.14" } ] } ] } ], "references": [ { "url": "https://git.kernel.org/stable/c/49100c0b070e900f87c8fac3be9b9ef8a30fa673" }, { "url": "https://git.kernel.org/stable/c/29124ae980e2860f0eec7355949d3d3292ee81da" }, { "url": "https://git.kernel.org/stable/c/c057ee03f751d6cecf7ee64f52f6545d94082aaa" }, { "url": "https://git.kernel.org/stable/c/75cfb92eb63298d717b6b0118f91ba12c4fcfeb5" }, { "url": "https://git.kernel.org/stable/c/60cf233b585cdf1f3c5e52d1225606b86acd08b0" } ], "title": "mm/migrate: fix shmem xarray update during migration", "x_generator": { "engine": "bippy-1.2.0" } }, "adp": [ { "title": "CVE Program Container", "references": [ { "url": "https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html" } ], "providerMetadata": { "orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE", "dateUpdated": "2025-11-03T19:41:00.297Z" } }, { "x_adpType": "supplier", "providerMetadata": { "orgId": "0b142b55-0307-4c5a-b3c9-f314f3fb7c5e", "shortName": "siemens-SADP", "dateUpdated": "2026-07-14T12:40:39.391Z" }, "affected": [ { "vendor": "Siemens", "product": "SIMATIC S7-1500 CPU 1518-4 PN/DP MFP", "versions": [ { "status": "affected", "version": "V3.1.6", "lessThan": "*", "versionType": "custom" } ], "defaultStatus": "unknown" }, { "vendor": "Siemens", "product": "SIMATIC S7-1500 CPU 1518-4 PN/DP MFP", "versions": [ { "status": "affected", "version": "V3.1.6", "lessThan": "*", "versionType": "custom" } ], "defaultStatus": "unknown" }, { "vendor": "Siemens", "product": "SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP", "versions": [ { "status": "affected", "version": "V3.1.6", "lessThan": "*", "versionType": "custom" } ], "defaultStatus": "unknown" }, { "vendor": "Siemens", "product": "SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP", "versions": [ { "status": "affected", "version": "V3.1.6", "lessThan": "*", "versionType": "custom" } ], "defaultStatus": "unknown" }, { "vendor": "Siemens", "product": "SIPLUS S7-1500 CPU 1518-4 PN/DP MFP", "versions": [ { "status": "affected", "version": "V3.1.6", "lessThan": "*", "versionType": "custom" } ], "defaultStatus": "unknown" } ], "references": [ { "url": "https://cert-portal.siemens.com/productcert/html/ssa-019113.html" } ] } ] } }