CVE-2025-38071: Linux kernel · x86/mm: Check return value from memblock_phys_alloc_range()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in dde4800d2b0f68b945fd81d4fc2d4a10ae25f743 : update Linux kernel when convenient.
Data as of 5 Nov 2026, 21:04 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-05.
- Patch
- Available – fixed in dde4800d2b0f68b945fd81d4fc2d4a10ae25f743, c6f2694c580c27dca0cf7546ee9b4bfa6b940e38, bffd5f2815c5234d609725cd0dc2f4bc5de2fc67 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: x86/mm: Check return value from memblock_phys_alloc_range() At least with CONFIG_PHYSICAL_START=0x100000, if there is < 4 MiB of contiguous free memory available at this point, the kernel will crash and burn because memblock_phys_alloc_range() returns 0 on failure, which leads memblock_phys_free() to throw the first 4 MiB of physical memory to the wolves. At a minimum it should fail gracefully with a meaningful diagnostic, but in fact everything seems to work fine without the weird reserve allocation.
References
- git.kernel.org/stable/c/8c18c904d301ffeb33b071eadc55cd6131e1e9be (opens in a new tab)
- git.kernel.org/stable/c/bffd5f2815c5234d609725cd0dc2f4bc5de2fc67 (opens in a new tab)
- git.kernel.org/stable/c/c6f2694c580c27dca0cf7546ee9b4bfa6b940e38 (opens in a new tab)
- git.kernel.org/stable/c/dde4800d2b0f68b945fd81d4fc2d4a10ae25f743 (opens in a new tab)
- git.kernel.org/stable/c/631ca8909fd5c62b9fda9edda93924311a78a9c4 (opens in a new tab)
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-082556.html (opens in a new tab)