CVE-2024-45022

published 11 Sep 2024 · updated 17 Nov 2026

mm/vmalloc: fix page mapping if vm_area_alloc_pages() with high order fallback to order 0

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel fd1ffbb50ef4da5e1378a46616b6d7407dc795da, Kernel 61ebe5a747da649057c37be1c37eb934b4af79ca, Kernel c91618816f4d21fc574d7577a37722adcd4075b2 and 4 more.

In the Linux kernel, the following vulnerability has been resolved: mm/vmalloc: fix page mapping if vm_area_alloc_pages() with high order fallback to order 0 The __vmap_pages_range_noflush() assumes its argument pages** contains pages with the same page shift. However, since commit e9c3cda4d86e ("mm, vmalloc: fix high order __GFP_NOFAIL allocations"), if gfp_flags includes __GFP_NOFAIL with high order in vm_area_alloc_pages() and page allocation failed for high order, the pages** may contain two different page shifts (high order and order-0). This could lead __vmap_pages_range_noflush() to perform incorrect mappings, potentially resulting in memory corruption. Users might encounter this as follows (vmap_allow_huge = true, 2M is for PMD_SIZE): kvmalloc(2M, __GFP_NOFAIL|GFP_X) __vmalloc_node_range_noprof(vm_flags=VM_ALLOW_HUGE_VMAP) vm_area_alloc_pages(order=9) ---> order-9 allocation failed and fallback to order-0 vmap_pages_range() vmap_pages_range_noflush() __vmap_pages_range_noflush(page_shift = 21) ----> wrong mapping happens We can remove the fallback code because if a high-order allocation fails, __vmalloc_node_range_noprof() will retry with order-0. Therefore, it is unnecessary to fallback to order-0 here. Therefore, fix this by removing the fallback code.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=fe5c2bdcb14c8612eb5e7a09159801c7219e9ac4 <fd1ffbb50ef4da5e1378a46616b6d7407dc795da, >=e9c3cda4d86e56bf7fe403729f38c4f0f65d3860 <61ebe5a747da649057c37be1c37eb934b4af79ca, >=e9c3cda4d86e56bf7fe403729f38c4f0f65d3860 <c91618816f4d21fc574d7577a37722adcd4075b2, >=e9c3cda4d86e56bf7fe403729f38c4f0f65d3860 <de7bad86345c43cd040ed43e20d9fad78a3ee59f, =6.3, >=6.1.95 <6.1.107fd1ffbb50ef4da5e1378a46616b6d7407dc795da, 61ebe5a747da649057c37be1c37eb934b4af79ca, c91618816f4d21fc574d7577a37722adcd4075b2, de7bad86345c43cd040ed43e20d9fad78a3ee59f, 6.1.107
linux-kernel: Kernel>=6.3.0 <6.6.48, >=6.7.0 <6.10.7, >=6.1.95 <6.1.1076.6.48, 6.10.7, 6.1.107

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2024-45022 severity on Zeptric[![CVE-2024-45022](https://zeptric.io/badge/cve/CVE-2024-45022.svg)](https://zeptric.io/cve/CVE-2024-45022)