GHSA-RMR6-R8PG-M34Q

Vulnerability from github – Published: 2026-07-25 12:31 – Updated: 2026-07-25 12:31
VLAI
Details

In the Linux kernel, the following vulnerability has been resolved:

x86/mm: Fix freeing of PMD-sized vmemmap pages

Commit bf9e4e30f353 ("x86/mm: use pagetable_free()"), switched from freeing non-boot page tables through __free_pages() to pagetable_free().

However, the function is also called to free vmemmap pages.

Given that vmemmap pages are not page tables, already the page_ptdesc(page) is wrong. But worse, pagetable_free() calls:

__free_pages(page, compound_order(page));

Since vmemmap pages are not compound pages (see vmemmap_alloc_block()) -- except for HVO, which doesn't apply here -- only first page of a PMD-sized vmemmap page is freed, leaking the other ones.

Fix it by properly decoupling pagetable and vmemmap freeing. free_pagetable() no longer has to mess with SECTION_INFO, as only the vmemmap is marked like that in register_page_bootmem_memmap().

The indentation in remove_pmd_table() is messed up. Fix that while touching it.

Bootmem info handling will soon be fixed up. For now, handle it similar to free_pagetable(), just avoiding the ifdef.

[ dhansen: changelog munging. More imperative voice ]

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-64302"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-07-25T10:17:11Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nx86/mm: Fix freeing of PMD-sized vmemmap pages\n\nCommit bf9e4e30f353 (\"x86/mm: use pagetable_free()\"), switched from\nfreeing non-boot page tables through __free_pages() to\npagetable_free().\n\nHowever, the function is also called to free vmemmap pages.\n\nGiven that vmemmap pages are not page tables, already the page_ptdesc(page)\nis wrong. But worse, pagetable_free() calls:\n\n\t__free_pages(page, compound_order(page));\n\nSince vmemmap pages are not compound pages (see vmemmap_alloc_block())\n-- except for HVO, which doesn\u0027t apply here -- only first page of a\nPMD-sized vmemmap page is freed, leaking the other ones.\n\nFix it by properly decoupling pagetable and vmemmap freeing.\nfree_pagetable() no longer has to mess with SECTION_INFO, as only the\nvmemmap is marked like that in register_page_bootmem_memmap().\n\nThe indentation in remove_pmd_table() is messed up. Fix that while\ntouching it.\n\nBootmem info handling will soon be fixed up. For now, handle it\nsimilar to free_pagetable(), just avoiding the ifdef.\n\n[ dhansen: changelog munging. More imperative voice ]",
  "id": "GHSA-rmr6-r8pg-m34q",
  "modified": "2026-07-25T12:31:30Z",
  "published": "2026-07-25T12:31:30Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-64302"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/03f6ecbc446c33b38fd452cd3c494092a8116967"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/39406c05f8f150f1685839acd38ffdd69ff92031"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/add1e4112e00b619614784bf630aeebfdefa23e1"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…