CVE-2025-37960

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> memblock: Accept allocated memory before use in memblock_double_array()<br /> <br /> When increasing the array size in memblock_double_array() and the slab<br /> is not yet available, a call to memblock_find_in_range() is used to<br /> reserve/allocate memory. However, the range returned may not have been<br /> accepted, which can result in a crash when booting an SNP guest:<br /> <br /> RIP: 0010:memcpy_orig+0x68/0x130<br /> Code: ...<br /> RSP: 0000:ffffffff9cc03ce8 EFLAGS: 00010006<br /> RAX: ff11001ff83e5000 RBX: 0000000000000000 RCX: fffffffffffff000<br /> RDX: 0000000000000bc0 RSI: ffffffff9dba8860 RDI: ff11001ff83e5c00<br /> RBP: 0000000000002000 R08: 0000000000000000 R09: 0000000000002000<br /> R10: 000000207fffe000 R11: 0000040000000000 R12: ffffffff9d06ef78<br /> R13: ff11001ff83e5000 R14: ffffffff9dba7c60 R15: 0000000000000c00<br /> memblock_double_array+0xff/0x310<br /> memblock_add_range+0x1fb/0x2f0<br /> memblock_reserve+0x4f/0xa0<br /> memblock_alloc_range_nid+0xac/0x130<br /> memblock_alloc_internal+0x53/0xc0<br /> memblock_alloc_try_nid+0x3d/0xa0<br /> swiotlb_init_remap+0x149/0x2f0<br /> mem_init+0xb/0xb0<br /> mm_core_init+0x8f/0x350<br /> start_kernel+0x17e/0x5d0<br /> x86_64_start_reservations+0x14/0x30<br /> x86_64_start_kernel+0x92/0xa0<br /> secondary_startup_64_no_verify+0x194/0x19b<br /> <br /> Mitigate this by calling accept_memory() on the memory range returned<br /> before the slab is available.<br /> <br /> Prior to v6.12, the accept_memory() interface used a &amp;#39;start&amp;#39; and &amp;#39;end&amp;#39;<br /> parameter instead of &amp;#39;start&amp;#39; and &amp;#39;size&amp;#39;, therefore the accept_memory()<br /> call must be adjusted to specify &amp;#39;start + size&amp;#39; for &amp;#39;end&amp;#39; when applying<br /> to kernels prior to v6.12.