Out-of-bounds Read in Linux

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 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.

Vulnerability class: Buffer Overflow

Published · last modified .

CVSS v3 metric

CVSS v3 base score 7.8 (High). Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

EPSS exploit prediction

EPSS 0.002, 11.6th percentile (last changed ); unchanged over 30 days. About EPSS.

Affected products

  • Linux — versions 8af1c121b0102041809bc137ec600d1865eaeedd, 6.6.72, 5.15.151
  • Linux Kernel — versions 6.8, 6.13

Weakness classification (CWE)

Public exploits and proof-of-concept code

Also mentioned in 3 other repositories (fkie-cad/nvd-json-data-feeds, oogasawa/Utility-security, w4zu/Debian_security). These reference the CVE in a list, notes or a scanner and are not exploit code for it.

References