Bug 2373332 (CVE-2025-38071) - CVE-2025-38071 kernel: x86/mm: Check return value from memblock_phys_alloc_range()
Summary: CVE-2025-38071 kernel: x86/mm: Check return value from memblock_phys_alloc_ra...
Keywords:
Status: NEW
Alias: CVE-2025-38071
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-06-18 10:02 UTC by OSIDB Bzimport
Modified: 2025-06-21 04:07 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-06-18 10:02:00 UTC
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.

Comment 1 Avinash Hanwate 2025-06-21 03:58:08 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025061838-CVE-2025-38071-cc7c@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.