Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-38071x86/mm: Check return value from memblock_phys_alloc_range()

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.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 17 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38071, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.19% · top 91% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected a7259df7670240ee03b0cfce8a3e5d3773911e24 – < 8c18c904d301ffeb33b071eadc55cd6131e1e9be
    • affected a7259df7670240ee03b0cfce8a3e5d3773911e24 – < bffd5f2815c5234d609725cd0dc2f4bc5de2fc67
    • affected a7259df7670240ee03b0cfce8a3e5d3773911e24 – < c6f2694c580c27dca0cf7546ee9b4bfa6b940e38
    • affected a7259df7670240ee03b0cfce8a3e5d3773911e24 – < dde4800d2b0f68b945fd81d4fc2d4a10ae25f743
    • affected a7259df7670240ee03b0cfce8a3e5d3773911e24 – < 631ca8909fd5c62b9fda9edda93924311a78a9c4
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 6.1.141 – ≤ 6.1.*
    • unaffected 6.6.93 – ≤ 6.6.*
    • unaffected 6.12.31 – ≤ 6.12.*
    • unaffected 6.14.9 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38071 badge
[![CVE-2025-38071](https://cveledger.app/badge/CVE-2025-38071.svg)](https://cveledger.app/cve/CVE-2025-38071)

Record last updated .