- Vulnerability/
- CVE-2024-57945
CVE-2024-57945: riscv: mm: Fix the out of bound issue of vmemmap address
First published: Tue Jan 21 2025(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | ||
| debian/linux | <=5.10.223-1<=5.10.234-1<=6.1.129-1<=6.1.128-1 | 6.12.20-1 6.12.21-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/a4a7ac3d266008018f05fae53060fcb331151a14
- https://git.kernel.org/stable/c/d2bd51954ac8377c2f1eb1813e694788998add66
- https://git.kernel.org/stable/c/f754f27e98f88428aaf6be6e00f5cbce97f62d4b
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-57945
- https://nvd.nist.gov/vuln/detail/CVE-2024-57945
- https://launchpad.net/bugs/cve/CVE-2024-57945
- https://security-tracker.debian.org/tracker/CVE-2024-57945
- https://ubuntu.com/security/CVE-2024-57945
- https://git.kernel.org/linus/f754f27e98f88428aaf6be6e00f5cbce97f62d4b
Frequently Asked Questions
What is the severity of CVE-2024-57945?
CVE-2024-57945 is classified as a medium severity vulnerability affecting the Linux kernel.
How do I fix CVE-2024-57945?
To fix CVE-2024-57945, upgrade to the latest stable version of the Linux kernel that includes the security patches.
Which systems are affected by CVE-2024-57945?
CVE-2024-57945 affects systems running certain versions of the Linux kernel that use the sparse vmemmap model.
What are the potential impacts of CVE-2024-57945?
The potential impacts of CVE-2024-57945 include possible system crashes or instability due to out-of-bounds memory access.
Is there a workaround for CVE-2024-57945?
There is no widely recommended workaround for CVE-2024-57945; updating the kernel is the best course of action.
- collector/mitre-cve
- source/MITRE
- agent/title
- agent/first-publish-date
- agent/type
- collector/nvd-api
- source/NVD
- agent/last-modified-date
- agent/author
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/usn-cve
- source/Ubuntu
- collector/nvd-cve
- collector/launchpad-cve
- source/Launchpad
- agent/references
- agent/source
- agent/description
- agent/tags
- agent/softwarecombine
- agent/event
- collector/security-tracker-debian
- source/Debian
- vendor/linux
- canonical/linux kernel
- package-manager/debian