Skip to main content
VulnerabilityPublished Updated

CVE-2025-37960: Linux kernel · memblock: Accept allocated memory before use in memblock_double_array()

Affects Linux kernelSource GCVE Database

0
Compare

Not known to be exploited.

Data as of 5 Nov 2026, 22:02 UTC

Severity
High

Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 May 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

AI-suggested

Apply the fix by ensuring accept_memory() is called on the allocated memory range before the slab allocator is available. For kernels prior to version 6.12, adjust the accept_memory() call parameters accordingly. Since this is a kernel-level issue, update to a kernel version that includes this fix once available.

Description

A vulnerability in the Linux kernel's memblock subsystem could cause a crash during booting of an SNP guest due to unaccepted allocated memory being used before acceptance in memblock_double_array(). This occurs when increasing the array size and the slab allocator is not yet available. The issue is mitigated by calling accept_memory() on the allocated memory range before the slab is available. The fix involves adjusting the accept_memory() call for kernels prior to version 6.12 due to parameter differences.

References

Community reviews

Loading reviews…