riscv: Sparse-Memory/vmemmap out-of-bounds fix
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
riscv: Sparse-Memory/vmemmap out-of-bounds fix
Offset vmemmap so that the first page of vmemmap will be mapped to the first page of physical memory in order to ensure that vmemmap’s bounds will be respected during pfn_to_page()/page_to_pfn() operations. The conversion macros will produce correct SV39/48/57 addresses for every possible/valid DRAM_BASE inside the physical memory limits.
v2:Address Alex's comments
From the CVE record · Linux
The Linux kernel’s RISC-V Sparse-Memory/vmemmap mapping can go out of bounds during pfn_to_page() and page_to_pfn() operations. The input does not specify how an attacker could trigger this, or any network, authentication, or user-interaction requirements.
Engineers running the Linux kernel on RISC-V should check their installations; affected versions are not specified.