riscv: mm: Fix the out of bound issue of vmemmap address
Summary
| CVE | CVE-2024-57945 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2025-01-21 13:15:09 UTC |
| Updated | 2026-06-01 17:16:32 UTC |
| 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. |
Risk And Classification
Primary CVSS: v3.1 7.1 HIGH from [email protected]
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Problem Types: CWE-125
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
HighIntegrity
NoneAvailability
HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Operating System | Linux | Linux Kernel | All | All | All | All |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 8af1c121b0102041809bc137ec600d1865eaeedd 04350304428063da6a55a8a4597d409dc69148b2 git | Not specified |
| CNA | Linux | Linux | affected 8310080799b40fd9f2a8b808c657269678c149af 92f08673d3f1893191323572f60e3c62f2e57c2f git | Not specified |
| CNA | Linux | Linux | affected a278d5c60f21aa15d540abb2f2da6e6d795c3e6e a4a7ac3d266008018f05fae53060fcb331151a14 git | Not specified |
| CNA | Linux | Linux | affected a11dd49dcb9376776193e15641f84fcc1e5980c9 d2bd51954ac8377c2f1eb1813e694788998add66 git | Not specified |
| CNA | Linux | Linux | affected a11dd49dcb9376776193e15641f84fcc1e5980c9 f754f27e98f88428aaf6be6e00f5cbce97f62d4b git | Not specified |
| CNA | Linux | Linux | affected 5941a90c55d3bfba732b32208d58d997600b44ef git | Not specified |
| CNA | Linux | Linux | affected 2a1728c15ec4f45ed9248ae22f626541c179bfbe git | Not specified |
| CNA | Linux | Linux | affected 5.10.212 5.10.258 semver | Not specified |
| CNA | Linux | Linux | affected 6.1.81 6.1.140 semver | Not specified |
| CNA | Linux | Linux | affected 6.6.21 6.6.72 semver | Not specified |
| CNA | Linux | Linux | affected 5.15.151 5.16 semver | Not specified |
| CNA | Linux | Linux | affected 6.7.9 6.8 semver | Not specified |
| CNA | Linux | Linux | affected 6.8 | Not specified |
| CNA | Linux | Linux | unaffected 6.8 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.10.258 5.10.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.140 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.72 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.10 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.13 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/a4a7ac3d266008018f05fae53060fcb331151a14 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/d2bd51954ac8377c2f1eb1813e694788998add66 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| lists.debian.org/debian-lts-announce/2025/08/msg00010.html | af854a3a-2127-422b-91ae-364da2661108 | lists.debian.org | |
| git.kernel.org/stable/c/04350304428063da6a55a8a4597d409dc69148b2 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/f754f27e98f88428aaf6be6e00f5cbce97f62d4b | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/92f08673d3f1893191323572f60e3c62f2e57c2f | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.