CVE-2025-22015 (GCVE-0-2025-22015)
Vulnerability from cvelistv5
Published
2025-04-08 08:18
Modified
2025-05-04 07:27
Severity ?
Summary
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.
References
Impacted products
Vendor Product Version
Linux Linux Version: be72d197b2281e2ee3f28017fc9be1ab17e26d16
Version: 07550b1461d4d0499165e7d6f7718cfd0e440427
Version: fc346d0a70a13d52fe1c4bc49516d83a42cd7c4c
Version: fc346d0a70a13d52fe1c4bc49516d83a42cd7c4c
Version: fc346d0a70a13d52fe1c4bc49516d83a42cd7c4c
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "mm/migrate.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "49100c0b070e900f87c8fac3be9b9ef8a30fa673",
              "status": "affected",
              "version": "be72d197b2281e2ee3f28017fc9be1ab17e26d16",
              "versionType": "git"
            },
            {
              "lessThan": "29124ae980e2860f0eec7355949d3d3292ee81da",
              "status": "affected",
              "version": "07550b1461d4d0499165e7d6f7718cfd0e440427",
              "versionType": "git"
            },
            {
              "lessThan": "c057ee03f751d6cecf7ee64f52f6545d94082aaa",
              "status": "affected",
              "version": "fc346d0a70a13d52fe1c4bc49516d83a42cd7c4c",
              "versionType": "git"
            },
            {
              "lessThan": "75cfb92eb63298d717b6b0118f91ba12c4fcfeb5",
              "status": "affected",
              "version": "fc346d0a70a13d52fe1c4bc49516d83a42cd7c4c",
              "versionType": "git"
            },
            {
              "lessThan": "60cf233b585cdf1f3c5e52d1225606b86acd08b0",
              "status": "affected",
              "version": "fc346d0a70a13d52fe1c4bc49516d83a42cd7c4c",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "mm/migrate.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.7"
            },
            {
              "lessThan": "6.7",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.132",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.85",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.21",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.13.*",
              "status": "unaffected",
              "version": "6.13.9",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.14",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.132",
                  "versionStartIncluding": "6.1.71",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.85",
                  "versionStartIncluding": "6.6.10",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.21",
                  "versionStartIncluding": "6.7",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.13.9",
                  "versionStartIncluding": "6.7",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.14",
                  "versionStartIncluding": "6.7",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "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-\u003emapping 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() \u0026\u0026 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-\u003emapping is NULL.  But fortunately,\nits caller split_huge_page_to_list_to_order() bails out early with EBUSY\nwhen folio-\u003emapping is NULL.  So no need to take care of it here."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-05-04T07:27:44.695Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "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"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-22015",
    "datePublished": "2025-04-08T08:18:05.287Z",
    "dateReserved": "2024-12-29T08:45:45.806Z",
    "dateUpdated": "2025-05-04T07:27:44.695Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2025-22015\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-04-08T09:15:26.150\",\"lastModified\":\"2025-04-08T18:13:53.347\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"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-\u003emapping 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() \u0026\u0026 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-\u003emapping is NULL.  But fortunately,\\nits caller split_huge_page_to_list_to_order() bails out early with EBUSY\\nwhen folio-\u003emapping is NULL.  So no need to take care of it here.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: mm/migrate: arregla la actualizaci\u00f3n de xarray de shmem durante la migraci\u00f3n un folio de shmem puede estar en la cach\u00e9 de p\u00e1gina o en la cach\u00e9 de intercambio, pero no al mismo tiempo. Es decir, una vez que est\u00e1 en la cach\u00e9 de intercambio, folio-\u0026gt;mapping debe ser NULL y el folio ya no est\u00e1 en una asignaci\u00f3n de shmem. En __folio_migrate_mapping(), para determinar el n\u00famero de entradas de xarray a actualizar, se usa folio_test_swapbacked(), pero eso combina shmem en el caso de la cach\u00e9 de p\u00e1gina y shmem en el caso de la cach\u00e9 de intercambio. Lleva a la corrupci\u00f3n de entradas de m\u00faltiples \u00edndices de xarray, ya que convierte una entrada hermana en una entrada normal durante xas_store() (vea [1] para una reproducci\u00f3n del espacio de usuario). Arr\u00e9glelo usando solo folio_test_swapcache() para determinar si xarray est\u00e1 almacenando entradas de cach\u00e9 de intercambio o no para elegir el n\u00famero correcto de entradas de xarray para actualizar. [1] https://lore.kernel.org/linux-mm/Z8idPCkaJW1IChjT@casper.infradead.org/ Nota: En __split_huge_page(), se usan folio_test_anon() y folio_test_swapcache() para obtener el espacio de direcciones de la cach\u00e9 de intercambio, pero esto ignora el folio shmem en el caso de la cach\u00e9 de intercambio. Esto podr\u00eda provocar la desreferenciaci\u00f3n de punteros nulos cuando un folio shmem en la cach\u00e9 de intercambio se divide en __xa_store(), ya que !folio_test_anon() es verdadero y folio-\u0026gt;mapping es nulo. Afortunadamente, su llamador, split_huge_page_to_list_to_order(), se detiene antes de tiempo con EBUSY cuando folio-\u0026gt;mapping es nulo. Por lo tanto, no es necesario ocuparse de ello aqu\u00ed.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/29124ae980e2860f0eec7355949d3d3292ee81da\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/49100c0b070e900f87c8fac3be9b9ef8a30fa673\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/60cf233b585cdf1f3c5e52d1225606b86acd08b0\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/75cfb92eb63298d717b6b0118f91ba12c4fcfeb5\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/c057ee03f751d6cecf7ee64f52f6545d94082aaa\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.