CVE-2024-57945 (GCVE-0-2024-57945)
Vulnerability from cvelistv5
Published
2025-01-21 12:18
Modified
2025-05-22 12:40
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: riscv: mm: Fix the out of bound issue of vmemmap address In sparse vmemmap model, the virtual address of vmemmap is calculated as: ((struct page *)VMEMMAP_START - (phys_ram_base >> PAGE_SHIFT)). And the struct page's va can be calculated with an offset: (vmemmap + (pfn)). However, when initializing struct pages, kernel actually starts from the first page from the same section that phys_ram_base belongs to. If the first page's physical address is not (phys_ram_base >> PAGE_SHIFT), then we get an va below VMEMMAP_START when calculating va for it's struct page. For example, if phys_ram_base starts from 0x82000000 with pfn 0x82000, the first page in the same section is actually pfn 0x80000. During init_unavailable_range(), we will initialize struct page for pfn 0x80000 with virtual address ((struct page *)VMEMMAP_START - 0x2000), which is below VMEMMAP_START as well as PCI_IO_END. This commit fixes this bug by introducing a new variable 'vmemmap_start_pfn' which is aligned with memory section size and using it to calculate vmemmap address instead of phys_ram_base.
References
Impacted products
Vendor Product Version
Linux Linux Version: 8310080799b40fd9f2a8b808c657269678c149af
Version: a278d5c60f21aa15d540abb2f2da6e6d795c3e6e
Version: a11dd49dcb9376776193e15641f84fcc1e5980c9
Version: a11dd49dcb9376776193e15641f84fcc1e5980c9
Version: 8af1c121b0102041809bc137ec600d1865eaeedd
Version: 5941a90c55d3bfba732b32208d58d997600b44ef
Version: 2a1728c15ec4f45ed9248ae22f626541c179bfbe
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "arch/riscv/include/asm/page.h",
            "arch/riscv/include/asm/pgtable.h",
            "arch/riscv/mm/init.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "92f08673d3f1893191323572f60e3c62f2e57c2f",
              "status": "affected",
              "version": "8310080799b40fd9f2a8b808c657269678c149af",
              "versionType": "git"
            },
            {
              "lessThan": "a4a7ac3d266008018f05fae53060fcb331151a14",
              "status": "affected",
              "version": "a278d5c60f21aa15d540abb2f2da6e6d795c3e6e",
              "versionType": "git"
            },
            {
              "lessThan": "d2bd51954ac8377c2f1eb1813e694788998add66",
              "status": "affected",
              "version": "a11dd49dcb9376776193e15641f84fcc1e5980c9",
              "versionType": "git"
            },
            {
              "lessThan": "f754f27e98f88428aaf6be6e00f5cbce97f62d4b",
              "status": "affected",
              "version": "a11dd49dcb9376776193e15641f84fcc1e5980c9",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "8af1c121b0102041809bc137ec600d1865eaeedd",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "5941a90c55d3bfba732b32208d58d997600b44ef",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "2a1728c15ec4f45ed9248ae22f626541c179bfbe",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "arch/riscv/include/asm/page.h",
            "arch/riscv/include/asm/pgtable.h",
            "arch/riscv/mm/init.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.8"
            },
            {
              "lessThan": "6.8",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.140",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.72",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.10",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.13",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.140",
                  "versionStartIncluding": "6.1.81",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.72",
                  "versionStartIncluding": "6.6.21",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.10",
                  "versionStartIncluding": "6.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.13",
                  "versionStartIncluding": "6.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionStartIncluding": "5.10.212",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionStartIncluding": "5.15.151",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionStartIncluding": "6.7.9",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nriscv: mm: Fix the out of bound issue of vmemmap address\n\nIn sparse vmemmap model, the virtual address of vmemmap is calculated as:\n((struct page *)VMEMMAP_START - (phys_ram_base \u003e\u003e PAGE_SHIFT)).\nAnd the struct page\u0027s va can be calculated with an offset:\n(vmemmap + (pfn)).\n\nHowever, when initializing struct pages, kernel actually starts from the\nfirst page from the same section that phys_ram_base belongs to. If the\nfirst page\u0027s physical address is not (phys_ram_base \u003e\u003e PAGE_SHIFT), then\nwe get an va below VMEMMAP_START when calculating va for it\u0027s struct page.\n\nFor example, if phys_ram_base starts from 0x82000000 with pfn 0x82000, the\nfirst page in the same section is actually pfn 0x80000. During\ninit_unavailable_range(), we will initialize struct page for pfn 0x80000\nwith virtual address ((struct page *)VMEMMAP_START - 0x2000), which is\nbelow VMEMMAP_START as well as PCI_IO_END.\n\nThis commit fixes this bug by introducing a new variable\n\u0027vmemmap_start_pfn\u0027 which is aligned with memory section size and using\nit to calculate vmemmap address instead of phys_ram_base."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-05-22T12:40:03.484Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/92f08673d3f1893191323572f60e3c62f2e57c2f"
        },
        {
          "url": "https://git.kernel.org/stable/c/a4a7ac3d266008018f05fae53060fcb331151a14"
        },
        {
          "url": "https://git.kernel.org/stable/c/d2bd51954ac8377c2f1eb1813e694788998add66"
        },
        {
          "url": "https://git.kernel.org/stable/c/f754f27e98f88428aaf6be6e00f5cbce97f62d4b"
        }
      ],
      "title": "riscv: mm: Fix the out of bound issue of vmemmap address",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-57945",
    "datePublished": "2025-01-21T12:18:12.548Z",
    "dateReserved": "2025-01-19T11:50:08.380Z",
    "dateUpdated": "2025-05-22T12:40:03.484Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-57945\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-01-21T13:15:09.033\",\"lastModified\":\"2025-05-22T13:15:55.070\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nriscv: mm: Fix the out of bound issue of vmemmap address\\n\\nIn sparse vmemmap model, the virtual address of vmemmap is calculated as:\\n((struct page *)VMEMMAP_START - (phys_ram_base \u003e\u003e PAGE_SHIFT)).\\nAnd the struct page\u0027s va can be calculated with an offset:\\n(vmemmap + (pfn)).\\n\\nHowever, when initializing struct pages, kernel actually starts from the\\nfirst page from the same section that phys_ram_base belongs to. If the\\nfirst page\u0027s physical address is not (phys_ram_base \u003e\u003e PAGE_SHIFT), then\\nwe get an va below VMEMMAP_START when calculating va for it\u0027s struct page.\\n\\nFor example, if phys_ram_base starts from 0x82000000 with pfn 0x82000, the\\nfirst page in the same section is actually pfn 0x80000. During\\ninit_unavailable_range(), we will initialize struct page for pfn 0x80000\\nwith virtual address ((struct page *)VMEMMAP_START - 0x2000), which is\\nbelow VMEMMAP_START as well as PCI_IO_END.\\n\\nThis commit fixes this bug by introducing a new variable\\n\u0027vmemmap_start_pfn\u0027 which is aligned with memory section size and using\\nit to calculate vmemmap address instead of phys_ram_base.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: riscv: mm: Corrige el problema de salida de l\u00edmites de la direcci\u00f3n vmemmap En el modelo vmemmap disperso, la direcci\u00f3n virtual de vmemmap se calcula como: ((struct page *)VMEMMAP_START - (phys_ram_base \u0026gt;\u0026gt; PAGE_SHIFT)). Y la va de la p\u00e1gina de estructura se puede calcular con un desplazamiento: (vmemmap + (pfn)). Sin embargo, al inicializar las p\u00e1ginas de estructura, el kernel en realidad comienza desde la primera p\u00e1gina de la misma secci\u00f3n a la que pertenece phys_ram_base. Si la direcci\u00f3n f\u00edsica de la primera p\u00e1gina no es (phys_ram_base \u0026gt;\u0026gt; PAGE_SHIFT), obtenemos una va por debajo de VMEMMAP_START al calcular la va para su p\u00e1gina de estructura. Por ejemplo, si phys_ram_base comienza desde 0x82000000 con pfn 0x82000, la primera p\u00e1gina en la misma secci\u00f3n es en realidad pfn 0x80000. Durante init_unavailable_range(), inicializaremos struct page para pfn 0x80000 con direcci\u00f3n virtual ((struct page *)VMEMMAP_START - 0x2000), que est\u00e1 debajo de VMEMMAP_START y PCI_IO_END. Esta confirmaci\u00f3n corrige este error al introducir una nueva variable \u0027vmemmap_start_pfn\u0027 que est\u00e1 alineada con el tama\u00f1o de la secci\u00f3n de memoria y la usa para calcular la direcci\u00f3n vmemmap en lugar de phys_ram_base.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/92f08673d3f1893191323572f60e3c62f2e57c2f\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/a4a7ac3d266008018f05fae53060fcb331151a14\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/d2bd51954ac8377c2f1eb1813e694788998add66\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/f754f27e98f88428aaf6be6e00f5cbce97f62d4b\",\"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.