Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 21 days later

    Published

  3. · 23 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-45022, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected fe5c2bdcb14c8612eb5e7a09159801c7219e9ac4 – < fd1ffbb50ef4da5e1378a46616b6d7407dc795da
    • affected e9c3cda4d86e56bf7fe403729f38c4f0f65d3860 – < de7bad86345c43cd040ed43e20d9fad78a3ee59f
    • affected e9c3cda4d86e56bf7fe403729f38c4f0f65d3860 – < c91618816f4d21fc574d7577a37722adcd4075b2
    • affected e9c3cda4d86e56bf7fe403729f38c4f0f65d3860 – < 61ebe5a747da649057c37be1c37eb934b4af79ca
    • affected 6.1.95 – < 6.1.107
  • Linux · Linux

    • affected 6.3
    • unaffected < 6.3
    • unaffected 6.1.107 – ≤ 6.1.*
    • unaffected 6.6.48 – ≤ 6.6.*
    • unaffected 6.10.7 – ≤ 6.10.*
    • unaffected 6.11 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-45022 badge
[![CVE-2024-45022](https://cveledger.app/badge/CVE-2024-45022.svg)](https://cveledger.app/cve/CVE-2024-45022)

Record last updated .