### [CVE-2025-38071](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-38071)
![](https://img.shields.io/static/v1?label=Product&message=Linux&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=n%2Fa&color=blue)

### 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 ofcontiguous free memory available at this point, the kernel will crashand burn because memblock_phys_alloc_range() returns 0 on failure,which leads memblock_phys_free() to throw the first 4 MiB of physicalmemory 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 reserveallocation.

### POC

#### Reference
No PoCs from references.

#### Github
- https://github.com/w4zu/Debian_security