GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel x86/mm: vmemmap pages freed as page tables leak memory on memory hot-remove

CVSS 5.5CVE-2026-64302Kernel, userspace & hypervisorcurated

Impact

After x86 switched non-boot page-table freeing to pagetable_free(), the same helper was still being used to free vmemmap pages. vmemmap pages are not compound pages, so pagetable_free()'s __free_pages(page, compound_order(page)) releases only the first page of a PMD-sized vmemmap allocation and leaks the rest, and the page_ptdesc() treatment of a non-page-table page is wrong to begin with. The result is unreclaimable memory lost on every memory hot-remove, growing with each cycle until the host is rebooted. This is a resource leak, not a memory-safety hole with a tenant-reachable path: only hosts that actually hot-remove memory - CXL capacity, balloon-driven or hotplug-capable VM hosts - accumulate it, and reaching the path takes administrative privilege, not a GPU pod.

Who can reach it

Local privileged operation only - the host's own memory hot-remove path, driven by root or the management plane. No unprivileged local user, guest or tenant path is described in the record.

What to do

Pick up a stable kernel carrying the fix (commits 03f6ecbc446c, 39406c05f8f1, add1e4112e00), which decouples vmemmap freeing from page-table freeing. A kernel update means draining and rebooting each host. Since the leak is only accrued by memory hot-remove, hosts that never hot-remove memory can wait for a routine kernel window rather than an out-of-band one. The kernel CNA's 5.5/AV:L score is its standard assignment for this class, not a measured severity.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.