CVE-2024-57945riscv: mm: Fix the out of bound issue of vmemmap address
- 7.8HighCVSS base score
- 0.21%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: riscv: mm: Fix the out of bound issue of vmemmap address In sparse vmemmap model, the virtual address of vmemmap is calculated as: ((struct page *)VMEMMAP_START - (phys_ram_base >> PAGE_SHIFT)). And the struct page's va can be calculated with an offset: (vmemmap + (pfn)). However, when initializing struct pages, kernel actually starts from the first page from the same section that phys_ram_base belongs to. If the first page's physical address is not (phys_ram_base >> PAGE_SHIFT), then we get an va below VMEMMAP_START when calculating va for it's struct page. For example, if phys_ram_base starts from 0x82000000 with pfn 0x82000, the first page in the same section is actually pfn 0x80000. During init_unavailable_range(), we will initialize struct page for pfn 0x80000 with virtual address ((struct page *)VMEMMAP_START - 0x2000), which is below VMEMMAP_START as well as PCI_IO_END. This commit fixes this bug by introducing a new variable 'vmemmap_start_pfn' which is aligned with memory section size and using it to calculate vmemmap address instead of phys_ram_base.
Timeline
ID reserved
By Linux
- 2 days later
· 2 days later
Published
- 19 months later
· 19 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.21% · top 88% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 8af1c121b0102041809bc137ec600d1865eaeedd – < 04350304428063da6a55a8a4597d409dc69148b2
- affected 8310080799b40fd9f2a8b808c657269678c149af – < 92f08673d3f1893191323572f60e3c62f2e57c2f
- affected a278d5c60f21aa15d540abb2f2da6e6d795c3e6e – < a4a7ac3d266008018f05fae53060fcb331151a14
- affected a11dd49dcb9376776193e15641f84fcc1e5980c9 – < d2bd51954ac8377c2f1eb1813e694788998add66
- affected a11dd49dcb9376776193e15641f84fcc1e5980c9 – < f754f27e98f88428aaf6be6e00f5cbce97f62d4b
- affected 5941a90c55d3bfba732b32208d58d997600b44ef
- affected 2a1728c15ec4f45ed9248ae22f626541c179bfbe
- affected 5.10.212 – < 5.10.258
- affected 6.1.81 – < 6.1.140
- affected 6.6.21 – < 6.6.72
- affected 5.15.151 – < 5.16
- affected 6.7.9 – < 6.8
- affected 6.8
- unaffected < 6.8
- unaffected 5.10.258 – ≤ 5.10.*
- unaffected 6.1.140 – ≤ 6.1.*
- unaffected 6.6.72 – ≤ 6.6.*
- unaffected 6.12.10 – ≤ 6.12.*
- unaffected 6.13 – ≤ *
References
References6
- https://git.kernel.org/stable/c/04350304428063da6a55a8a4597d409dc69148b2 (opens in a new tab)
- https://git.kernel.org/stable/c/92f08673d3f1893191323572f60e3c62f2e57c2f (opens in a new tab)
- https://git.kernel.org/stable/c/a4a7ac3d266008018f05fae53060fcb331151a14 (opens in a new tab)
- https://git.kernel.org/stable/c/d2bd51954ac8377c2f1eb1813e694788998add66 (opens in a new tab)
- https://git.kernel.org/stable/c/f754f27e98f88428aaf6be6e00f5cbce97f62d4b (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/08/msg00010.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-53848 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-57945)Record last updated .