{"uuid": "178ccb6a-bf9d-4a76-85c2-8b98f344a074", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-38071", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/18710", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-38071\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nx86/mm: Check return value from memblock_phys_alloc_range()\n\nAt least with CONFIG_PHYSICAL_START=0x100000, if there is < 4 MiB of\ncontiguous free memory available at this point, the kernel will crash\nand burn because memblock_phys_alloc_range() returns 0 on failure,\nwhich leads memblock_phys_free() to throw the first 4 MiB of physical\nmemory to the wolves.\n\nAt a minimum it should fail gracefully with a meaningful diagnostic,\nbut in fact everything seems to work fine without the weird reserve\nallocation.\n\ud83d\udccf Published: 2025-06-18T09:33:47.975Z\n\ud83d\udccf Modified: 2025-06-18T09:33:47.975Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/8c18c904d301ffeb33b071eadc55cd6131e1e9be\n2. https://git.kernel.org/stable/c/bffd5f2815c5234d609725cd0dc2f4bc5de2fc67\n3. https://git.kernel.org/stable/c/c6f2694c580c27dca0cf7546ee9b4bfa6b940e38\n4. https://git.kernel.org/stable/c/dde4800d2b0f68b945fd81d4fc2d4a10ae25f743\n5. https://git.kernel.org/stable/c/631ca8909fd5c62b9fda9edda93924311a78a9c4", "creation_timestamp": "2025-06-18T10:40:10.000000Z"}