CVE-2025-38071: x86/mm: Check return value from memblock_phys_alloc_range()
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 631ca8909fd5c62b9fda9edda93924311a78a9c4, 8c18c904d301ffeb33b071eadc55cd6131e1e9be, bffd5f2815c5234d609725cd0dc2f4bc5de2fc67.
Low priority for now. Upgrade to Linux Linux 631ca8909fd5c62b9fda9edda93924311a78a9c4, 8c18c904d301ffeb33b071eadc55cd6131e1e9be, bffd5f2815c5234d609725cd0dc2f4bc5de2fc67 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jun 18, 2025
- Updated
- Nov 5, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernelbefore 6.1.141
- linux linux kernel6.2 and later · before 6.6.93
- linux linux kernel6.7 and later · before 6.12.31
- linux linux kernel6.13 and later · before 6.14.9
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.15affected
- a7259df7670240ee03b0cfce8a3e5d3773911e24 and later · before 8c18c904d301ffeb33b071eadc55cd6131e1e9beaffected · git
- a7259df7670240ee03b0cfce8a3e5d3773911e24 and later · before bffd5f2815c5234d609725cd0dc2f4bc5de2fc67affected · git
- a7259df7670240ee03b0cfce8a3e5d3773911e24 and later · before c6f2694c580c27dca0cf7546ee9b4bfa6b940e38affected · git
- a7259df7670240ee03b0cfce8a3e5d3773911e24 and later · before dde4800d2b0f68b945fd81d4fc2d4a10ae25f743affected · git
- a7259df7670240ee03b0cfce8a3e5d3773911e24 and later · before 631ca8909fd5c62b9fda9edda93924311a78a9c4affected · git
- before 5.15not affected · semver
- 6.1.141 and later · up to and including 6.1.*not affected · semver
- 6.6.93 and later · up to and including 6.6.*not affected · semver
- 6.12.31 and later · up to and including 6.12.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.147-1 | 6.1.147-1 |
| Debian:13 | linux | before 6.12.32-1 | 6.12.32-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38067Jun 18, 2025 · rseq: Fix segfault on registration when rseq_cs is non-zero22Monitor
- ← EarlierCVE-2025-38069Jun 18, 2025 · PCI: endpoint: pci-epf-test: Fix double free that causes kernel to oops31Monitor
- Later →CVE-2025-38072Jun 18, 2025 · libnvdimm/labels: Fix divide error in nd_label_data_init()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 631ca8909fd5c62b9fda9edda93924311a78a9c4 | Vendor (CNA) |
| Linux Linux | 8c18c904d301ffeb33b071eadc55cd6131e1e9be | Vendor (CNA) |
| Linux Linux | bffd5f2815c5234d609725cd0dc2f4bc5de2fc67 | Vendor (CNA) |
| Linux Linux | c6f2694c580c27dca0cf7546ee9b4bfa6b940e38 | Vendor (CNA) |
| Linux Linux | dde4800d2b0f68b945fd81d4fc2d4a10ae25f743 | Vendor (CNA) |
| debian:linux | 6.1.147-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/8c18c904d301ffeb33b071eadc55cd6131e1e9be
- git.kernel.org/stable/c/bffd5f2815c5234d609725cd0dc2f4bc5de2fc67
- git.kernel.org/stable/c/c6f2694c580c27dca0cf7546ee9b4bfa6b940e38
- git.kernel.org/stable/c/dde4800d2b0f68b945fd81d4fc2d4a10ae25f743
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
- cert-portal.siemens.com/productcert/html/ssa-082556.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.