CVE-2025-37960 (GCVE-0-2025-37960)
Vulnerability from cvelistv5
Published
2025-05-20 16:01
Modified
2025-05-26 05:24
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: memblock: Accept allocated memory before use in memblock_double_array() When increasing the array size in memblock_double_array() and the slab is not yet available, a call to memblock_find_in_range() is used to reserve/allocate memory. However, the range returned may not have been accepted, which can result in a crash when booting an SNP guest: RIP: 0010:memcpy_orig+0x68/0x130 Code: ... RSP: 0000:ffffffff9cc03ce8 EFLAGS: 00010006 RAX: ff11001ff83e5000 RBX: 0000000000000000 RCX: fffffffffffff000 RDX: 0000000000000bc0 RSI: ffffffff9dba8860 RDI: ff11001ff83e5c00 RBP: 0000000000002000 R08: 0000000000000000 R09: 0000000000002000 R10: 000000207fffe000 R11: 0000040000000000 R12: ffffffff9d06ef78 R13: ff11001ff83e5000 R14: ffffffff9dba7c60 R15: 0000000000000c00 memblock_double_array+0xff/0x310 memblock_add_range+0x1fb/0x2f0 memblock_reserve+0x4f/0xa0 memblock_alloc_range_nid+0xac/0x130 memblock_alloc_internal+0x53/0xc0 memblock_alloc_try_nid+0x3d/0xa0 swiotlb_init_remap+0x149/0x2f0 mem_init+0xb/0xb0 mm_core_init+0x8f/0x350 start_kernel+0x17e/0x5d0 x86_64_start_reservations+0x14/0x30 x86_64_start_kernel+0x92/0xa0 secondary_startup_64_no_verify+0x194/0x19b Mitigate this by calling accept_memory() on the memory range returned before the slab is available. Prior to v6.12, the accept_memory() interface used a 'start' and 'end' parameter instead of 'start' and 'size', therefore the accept_memory() call must be adjusted to specify 'start + size' for 'end' when applying to kernels prior to v6.12.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/7bcd29181bab8d508d2adfdbb132de8b1e088698
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/aa513e69e011a2b19fa22ce62ce35effbd5e0c81
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/d66a22f6a432a9dd376c9b365d7dc89bd416909c
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/da8bf5daa5e55a6af2b285ecda460d6454712ff4
Impacted products
Vendor Product Version
Linux Linux Version: dcdfdd40fa82b6704d2841938e5c8ec3051eb0d6
Version: dcdfdd40fa82b6704d2841938e5c8ec3051eb0d6
Version: dcdfdd40fa82b6704d2841938e5c8ec3051eb0d6
Version: dcdfdd40fa82b6704d2841938e5c8ec3051eb0d6
 Create a notification for this product.
   Linux Linux Version: 6.5
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "mm/memblock.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "7bcd29181bab8d508d2adfdbb132de8b1e088698",
              "status": "affected",
              "version": "dcdfdd40fa82b6704d2841938e5c8ec3051eb0d6",
              "versionType": "git"
            },
            {
              "lessThan": "d66a22f6a432a9dd376c9b365d7dc89bd416909c",
              "status": "affected",
              "version": "dcdfdd40fa82b6704d2841938e5c8ec3051eb0d6",
              "versionType": "git"
            },
            {
              "lessThan": "aa513e69e011a2b19fa22ce62ce35effbd5e0c81",
              "status": "affected",
              "version": "dcdfdd40fa82b6704d2841938e5c8ec3051eb0d6",
              "versionType": "git"
            },
            {
              "lessThan": "da8bf5daa5e55a6af2b285ecda460d6454712ff4",
              "status": "affected",
              "version": "dcdfdd40fa82b6704d2841938e5c8ec3051eb0d6",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "mm/memblock.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.5"
            },
            {
              "lessThan": "6.5",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.92",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.29",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.14.*",
              "status": "unaffected",
              "version": "6.14.7",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.15",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.92",
                  "versionStartIncluding": "6.5",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.29",
                  "versionStartIncluding": "6.5",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.14.7",
                  "versionStartIncluding": "6.5",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.15",
                  "versionStartIncluding": "6.5",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmemblock: Accept allocated memory before use in memblock_double_array()\n\nWhen increasing the array size in memblock_double_array() and the slab\nis not yet available, a call to memblock_find_in_range() is used to\nreserve/allocate memory. However, the range returned may not have been\naccepted, which can result in a crash when booting an SNP guest:\n\n  RIP: 0010:memcpy_orig+0x68/0x130\n  Code: ...\n  RSP: 0000:ffffffff9cc03ce8 EFLAGS: 00010006\n  RAX: ff11001ff83e5000 RBX: 0000000000000000 RCX: fffffffffffff000\n  RDX: 0000000000000bc0 RSI: ffffffff9dba8860 RDI: ff11001ff83e5c00\n  RBP: 0000000000002000 R08: 0000000000000000 R09: 0000000000002000\n  R10: 000000207fffe000 R11: 0000040000000000 R12: ffffffff9d06ef78\n  R13: ff11001ff83e5000 R14: ffffffff9dba7c60 R15: 0000000000000c00\n  memblock_double_array+0xff/0x310\n  memblock_add_range+0x1fb/0x2f0\n  memblock_reserve+0x4f/0xa0\n  memblock_alloc_range_nid+0xac/0x130\n  memblock_alloc_internal+0x53/0xc0\n  memblock_alloc_try_nid+0x3d/0xa0\n  swiotlb_init_remap+0x149/0x2f0\n  mem_init+0xb/0xb0\n  mm_core_init+0x8f/0x350\n  start_kernel+0x17e/0x5d0\n  x86_64_start_reservations+0x14/0x30\n  x86_64_start_kernel+0x92/0xa0\n  secondary_startup_64_no_verify+0x194/0x19b\n\nMitigate this by calling accept_memory() on the memory range returned\nbefore the slab is available.\n\nPrior to v6.12, the accept_memory() interface used a \u0027start\u0027 and \u0027end\u0027\nparameter instead of \u0027start\u0027 and \u0027size\u0027, therefore the accept_memory()\ncall must be adjusted to specify \u0027start + size\u0027 for \u0027end\u0027 when applying\nto kernels prior to v6.12."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-05-26T05:24:36.480Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/7bcd29181bab8d508d2adfdbb132de8b1e088698"
        },
        {
          "url": "https://git.kernel.org/stable/c/d66a22f6a432a9dd376c9b365d7dc89bd416909c"
        },
        {
          "url": "https://git.kernel.org/stable/c/aa513e69e011a2b19fa22ce62ce35effbd5e0c81"
        },
        {
          "url": "https://git.kernel.org/stable/c/da8bf5daa5e55a6af2b285ecda460d6454712ff4"
        }
      ],
      "title": "memblock: Accept allocated memory before use in memblock_double_array()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-37960",
    "datePublished": "2025-05-20T16:01:53.264Z",
    "dateReserved": "2025-04-16T04:51:23.974Z",
    "dateUpdated": "2025-05-26T05:24:36.480Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2025-37960\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-05-20T16:15:34.267\",\"lastModified\":\"2025-05-22T13:15:56.003\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nmemblock: Accept allocated memory before use in memblock_double_array()\\n\\nWhen increasing the array size in memblock_double_array() and the slab\\nis not yet available, a call to memblock_find_in_range() is used to\\nreserve/allocate memory. However, the range returned may not have been\\naccepted, which can result in a crash when booting an SNP guest:\\n\\n  RIP: 0010:memcpy_orig+0x68/0x130\\n  Code: ...\\n  RSP: 0000:ffffffff9cc03ce8 EFLAGS: 00010006\\n  RAX: ff11001ff83e5000 RBX: 0000000000000000 RCX: fffffffffffff000\\n  RDX: 0000000000000bc0 RSI: ffffffff9dba8860 RDI: ff11001ff83e5c00\\n  RBP: 0000000000002000 R08: 0000000000000000 R09: 0000000000002000\\n  R10: 000000207fffe000 R11: 0000040000000000 R12: ffffffff9d06ef78\\n  R13: ff11001ff83e5000 R14: ffffffff9dba7c60 R15: 0000000000000c00\\n  memblock_double_array+0xff/0x310\\n  memblock_add_range+0x1fb/0x2f0\\n  memblock_reserve+0x4f/0xa0\\n  memblock_alloc_range_nid+0xac/0x130\\n  memblock_alloc_internal+0x53/0xc0\\n  memblock_alloc_try_nid+0x3d/0xa0\\n  swiotlb_init_remap+0x149/0x2f0\\n  mem_init+0xb/0xb0\\n  mm_core_init+0x8f/0x350\\n  start_kernel+0x17e/0x5d0\\n  x86_64_start_reservations+0x14/0x30\\n  x86_64_start_kernel+0x92/0xa0\\n  secondary_startup_64_no_verify+0x194/0x19b\\n\\nMitigate this by calling accept_memory() on the memory range returned\\nbefore the slab is available.\\n\\nPrior to v6.12, the accept_memory() interface used a \u0027start\u0027 and \u0027end\u0027\\nparameter instead of \u0027start\u0027 and \u0027size\u0027, therefore the accept_memory()\\ncall must be adjusted to specify \u0027start + size\u0027 for \u0027end\u0027 when applying\\nto kernels prior to v6.12.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: memblock: aceptar memoria asignada antes de su uso en memblock_double_array(). Al aumentar el tama\u00f1o de la matriz en memblock_double_array() y la losa a\u00fan no est\u00e1 disponible, se utiliza una llamada a memblock_find_in_range() para reservar/asignar memoria. Sin embargo, es posible que no se haya aceptado el rango devuelto, lo que puede provocar un bloqueo al iniciar un invitado SNP: RIP: 0010:memcpy_orig+0x68/0x130 C\u00f3digo: ... RSP: 0000:ffffffff9cc03ce8 EFLAGS: 00010006 RAX: ff11001ff83e5000 RBX: 0000000000000000 RCX: fffffffffffff000 RDX: 0000000000000bc0 RSI: ffffffff9dba8860 RDI: ff11001ff83e5c00 RBP: 0000000000002000 R08: 000000000000000 R09: 0000000000002000 R10: 000000207fffe000 R11: 0000040000000000 R12: ffffffff9d06ef78 R13: ff11001ff83e5000 R14: ffffffff9dba7c60 R15: 0000000000000c00 memblock_double_array+0xff/0x310 memblock_add_range+0x1fb/0x2f0 memblock_reserve+0x4f/0xa0 memblock_alloc_range_nid+0xac/0x130 memblock_alloc_internal+0x53/0xc0 memblock_alloc_try_nid+0x3d/0xa0 swiotlb_init_remap+0x149/0x2f0 mem_init+0xb/0xb0 mm_core_init+0x8f/0x350 start_kernel+0x17e/0x5d0 x86_64_start_reservations+0x14/0x30 x86_64_start_kernel+0x92/0xa0 secondary_startup_64_no_verify+0x194/0x19b Para mitigar este problema, llame a accept_memory() en el rango de memoria devuelto antes de que el slab est\u00e9 disponible. Antes de la versi\u00f3n 6.12, la interfaz accept_memory() utilizaba los par\u00e1metros \\\"start\\\" y \\\"end\\\" en lugar de \\\"start\\\" y \\\"size\\\". Por lo tanto, la llamada a accept_memory() debe ajustarse para especificar \\\"start + size\\\" en lugar de \\\"end\\\" al aplicarlo a kernels anteriores a la versi\u00f3n 6.12.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/7bcd29181bab8d508d2adfdbb132de8b1e088698\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/aa513e69e011a2b19fa22ce62ce35effbd5e0c81\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/d66a22f6a432a9dd376c9b365d7dc89bd416909c\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/da8bf5daa5e55a6af2b285ecda460d6454712ff4\",\"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.
  • 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.