CVE-2024-45022
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2024-45022
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2024-45022.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2024-45022
- Downstream
- Related
- Published
- 2024-09-11T15:13:55Z
- Modified
- 2025-10-17T12:08:16.375319Z
- Summary
- mm/vmalloc: fix page mapping if vm_area_alloc_pages() with high order fallback to order 0
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
mm/vmalloc: fix page mapping if vmareaalloc_pages() with high order fallback to order 0
The _vmappagesrangenoflush() 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 _vmappagesrangenoflush() to perform incorrect mappings, potentially resulting in memory corruption.
Users might encounter this as follows (vmapallowhuge = true, 2M is for PMD_SIZE):
kvmalloc(2M, _GFPNOFAIL|GFPX) _vmallocnoderangenoprof(vmflags=VMALLOWHUGEVMAP) vmareaallocpages(order=9) ---> order-9 allocation failed and fallback to order-0 vmappagesrange() vmappagesrangenoflush() _vmappagesrangenoflush(pageshift = 21) ----> wrong mapping happens
We can remove the fallback code because if a high-order allocation fails, _vmallocnoderangenoprof() will retry with order-0. Therefore, it is unnecessary to fallback to order-0 here. Therefore, fix this by removing the fallback code.
- References
-
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- https://git.kernel.org/stable/c/61ebe5a747da649057c37be1c37eb934b4af79ca
- https://git.kernel.org/stable/c/c91618816f4d21fc574d7577a37722adcd4075b2
- https://git.kernel.org/stable/c/de7bad86345c43cd040ed43e20d9fad78a3ee59f
- https://git.kernel.org/stable/c/fd1ffbb50ef4da5e1378a46616b6d7407dc795da
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducedfe5c2bdcb14c8612eb5e7a09159801c7219e9ac4Fixedfd1ffbb50ef4da5e1378a46616b6d7407dc795da
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducede9c3cda4d86e56bf7fe403729f38c4f0f65d3860Fixedde7bad86345c43cd040ed43e20d9fad78a3ee59f
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducede9c3cda4d86e56bf7fe403729f38c4f0f65d3860Fixedc91618816f4d21fc574d7577a37722adcd4075b2
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducede9c3cda4d86e56bf7fe403729f38c4f0f65d3860Fixed61ebe5a747da649057c37be1c37eb934b4af79ca