CVE-2024-56677

In the Linux kernel, the following vulnerability has been resolved: powerpc/fadump: Move fadump_cma_init to setup_arch() after initmem_init() During early init CMA_MIN_ALIGNMENT_BYTES can be PAGE_SIZE, since pageblock_order is still zero and it gets initialized later during initmem_init() e.g. setup_arch() -> initmem_init() -> sparse_init() -> set_pageblock_order() One such use case where this causes issue is - early_setup() -> early_init_devtree() -> fadump_reserve_mem() -> fadump_cma_init() This causes CMA memory alignment check to be bypassed in cma_init_reserved_mem(). Then later cma_activate_area() can hit a VM_BUG_ON_PAGE(pfn & ((1 << order) - 1)) if the reserved memory area was not pageblock_order aligned. Fix it by moving the fadump_cma_init() after initmem_init(), where other such cma reservations also gets called. <stack trace> ============== page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x10010 flags: 0x13ffff800000000(node=1|zone=0|lastcpupid=0x7ffff) CMA raw: 013ffff800000000 5deadbeef0000100 5deadbeef0000122 0000000000000000 raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: VM_BUG_ON_PAGE(pfn & ((1 << order) - 1)) ------------[ cut here ]------------ kernel BUG at mm/page_alloc.c:778! Call Trace: __free_one_page+0x57c/0x7b0 (unreliable) free_pcppages_bulk+0x1a8/0x2c8 free_unref_page_commit+0x3d4/0x4e4 free_unref_page+0x458/0x6d0 init_cma_reserved_pageblock+0x114/0x198 cma_init_reserved_areas+0x270/0x3e0 do_one_initcall+0x80/0x2f8 kernel_init_freeable+0x33c/0x530 kernel_init+0x34/0x26c ret_from_kernel_user_thread+0x14/0x1c
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

History

26 Sep 2025, 20:27

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/05b94cae1c47f94588c3e7096963c1007c4d9c1d - () https://git.kernel.org/stable/c/05b94cae1c47f94588c3e7096963c1007c4d9c1d - Patch
References () https://git.kernel.org/stable/c/7351c5a6507b4401aeecadb5959131410a339520 - () https://git.kernel.org/stable/c/7351c5a6507b4401aeecadb5959131410a339520 - Patch
References () https://git.kernel.org/stable/c/aabef6301dcf410dfd2b8759cd413b2a003c7e3f - () https://git.kernel.org/stable/c/aabef6301dcf410dfd2b8759cd413b2a003c7e3f - Patch
References () https://git.kernel.org/stable/c/c5c1d1ef70834013fc3bd12b6a0f4664c6d75a74 - () https://git.kernel.org/stable/c/c5c1d1ef70834013fc3bd12b6a0f4664c6d75a74 - Patch
References () https://git.kernel.org/stable/c/f551637fe9bf863386309e03f9d148d97f535ad1 - () https://git.kernel.org/stable/c/f551637fe9bf863386309e03f9d148d97f535ad1 - Patch
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: powerpc/fadump: mover fadump_cma_init a setup_arch() después de initmem_init() Durante la inicialización temprana, CMA_MIN_ALIGNMENT_BYTES puede ser PAGE_SIZE, ya que pageblock_order sigue siendo cero y se inicializa más tarde durante initmem_init(), por ejemplo, setup_arch() -&gt; initmem_init() -&gt; sparse_init() -&gt; set_pageblock_order() Un caso de uso en el que esto causa problemas es: early_setup() -&gt; early_init_devtree() -&gt; fadump_reserve_mem() -&gt; fadump_cma_init() Esto hace que la verificación de alineación de memoria de CMA se omita en cma_init_reserved_mem(). Luego, más adelante, cma_activate_area() puede generar un error VM_BUG_ON_PAGE(pfn &amp; ((1 &lt;&lt; order) - 1)) si el área de memoria reservada no estaba alineada con pageblock_order. Solucione este problema moviendo fadump_cma_init() después de initmem_init(), donde también se invocan otras reservas de cma similares. ============== página: refcount:0 mapcount:0 mapping:0000000000000000 índice:0x0 pfn:0x10010 indicadores: 0x13ffff800000000(nodo=1|zona=0|lastcpupid=0x7ffff) CMA sin procesar: 013ffff800000000 5deadbeef0000100 5deadbeef0000122 000000000000000 sin procesar: 000000000000000 00000000000000 000000000000 00000000ffffffff 0000000000000000 página volcada porque: VM_BUG_ON_PAGE(pfn &amp; ((1 &lt;&lt; orden) - 1)) ------------[ cortar aquí ]------------ ¡ERROR del kernel en mm/page_alloc.c:778! Seguimiento de llamadas: __free_one_page+0x57c/0x7b0 (no confiable) free_pcppages_bulk+0x1a8/0x2c8 free_unref_page_commit+0x3d4/0x4e4 free_unref_page+0x458/0x6d0 init_cma_reserved_pageblock+0x114/0x198 cma_init_reserved_areas+0x270/0x3e0 do_one_initcall+0x80/0x2f8 kernel_init_freeable+0x33c/0x530 kernel_init+0x34/0x26c ret_from_kernel_user_thread+0x14/0x1c
CVSS v2 : unknown
v3 : unknown
v2 : unknown
v3 : 5.5
CWE CWE-908
CPE cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
First Time Linux linux Kernel
Linux

28 Dec 2024, 10:15

Type Values Removed Values Added
New CVE

Information

Published : 2024-12-28 10:15

Updated : 2025-09-26 20:27


NVD link : CVE-2024-56677

Mitre link : CVE-2024-56677

CVE.ORG link : CVE-2024-56677


JSON object : View

Products Affected

linux

  • linux_kernel
CWE
CWE-908

Use of Uninitialized Resource