cbcvebase.
CVE-2024-57945
published 2025-01-21

CVE-2024-57945: 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…

PriorityP428high7.1CVSS 3.1
AVLACLPRLUINSUCHINAH
EPSS
0.21%
11.0th percentile
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.

Affected

33 ranges· showing 25
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.140-1 (bookworm)linux 6.1.140-1 (bookworm)
debianlinux-6.1< linux 6.1.140-1 (bookworm)linux 6.1.140-1 (bookworm)
linuxlinux
linuxlinux
linuxlinux
linuxlinux>= 5.10.212 < 5.10.2585.10.258
linuxlinux>= 5.15.151 < 5.165.16
linuxlinux>= 6.1.81 < 6.1.1406.1.140
linuxlinux>= 6.6.21 < 6.6.726.6.72
linuxlinux>= 6.7.9 < 6.86.8
linuxlinux>= 8310080799b40fd9f2a8b808c657269678c149af < 92f08673d3f1893191323572f60e3c62f2e57c2f92f08673d3f1893191323572f60e3c62f2e57c2f
linuxlinux>= 8af1c121b0102041809bc137ec600d1865eaeedd < 04350304428063da6a55a8a4597d409dc69148b204350304428063da6a55a8a4597d409dc69148b2
linuxlinux>= a11dd49dcb9376776193e15641f84fcc1e5980c9 < d2bd51954ac8377c2f1eb1813e694788998add66d2bd51954ac8377c2f1eb1813e694788998add66
linuxlinux>= a11dd49dcb9376776193e15641f84fcc1e5980c9 < f754f27e98f88428aaf6be6e00f5cbce97f62d4bf754f27e98f88428aaf6be6e00f5cbce97f62d4b
linuxlinux>= a278d5c60f21aa15d540abb2f2da6e6d795c3e6e < a4a7ac3d266008018f05fae53060fcb331151a14a4a7ac3d266008018f05fae53060fcb331151a14
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel
linuxlinux_kernel>= 0 < 6.1.140-16.1.140-1
linuxlinux_kernel>= 0 < 6.12.10-16.12.10-1

CVSS provenance

nvdv3.17.1HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
osv7.8HIGH
vendor_ubuntu7.8HIGH
vendor_debian7.1HIGH
vendor_redhat7.1HIGH
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.