CVE-2025-38071

Boot-time crash via unchecked physical allocation

Published Jun 18, 2025 · Updated Jul 14, 2026

Improper input validation in Linux and Siemens GNU/Linux firmware allows local users to trigger a boot-time system crash. In arch/x86/mm/init.c, code fails to check whether memblock_phys_alloc_range() returned zero before passing that address to memblock_phys_free(), which releases the first 4 MiB of physical memory. The path requires CONFIG_PHYSICAL_START=0x100000 and less than 4 MiB of contiguous free memory at allocation time; the documented consequence is a crash, not data disclosure or code execution.

CVSS severity5.5
Medium
EPSS probability0.17%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper input validation in Linux and Siemens GNU/Linux firmware allows local users to trigger a boot-time system crash. In arch/x86/mm/init.c, code fails to check whether memblock_phys_alloc_range() returned zero before passing that address to memblock_phys_free(), which releases the first 4 MiB of physical memory. The path requires CONFIG_PHYSICAL_START=0x100000 and less than 4 MiB of contiguous free memory at allocation time; the documented consequence is a crash, not data disclosure or code execution.

The record

CVE
CVE-2025-38071
Published
Jun 18, 2025
Updated
Jul 14, 2026
Vendor
Siemens
Product
SIPLUS S7-1500 CPU 1518-4 PN/DP MFP
Classifications
CWE-20, T1499, T0814
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jun 18, 2025CVE publishedPublication date reported by the CVE source.
  2. Jul 14, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=V3.1.5 <*

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Siemens · SIPLUS S7-1500 CPU 1518-4 PN/DP MFPversion=V3.1.5 <*
The Linux Kernel Organization · Linuxversion=5.15; version=a7259df7670240ee03b0cfce8a3e5d3773911e24 <631ca8909fd5c62b9fda9edda93924311a78a9c4; version=a7259df7670240ee03b0cfce8a3e5d3773911e24 <8c18c904d301ffeb33b071eadc55cd6131e1e9be; version=a7259df7670240ee03b0cfce8a3e5d3773911e24 <bffd5f2815c5234d609725cd0dc2f4bc5de2fc67; version=a7259df7670240ee03b0cfce8a3e5d3773911e24 <c6f2694c580c27dca0cf7546ee9b4bfa6b940e38; version=a7259df7670240ee03b0cfce8a3e5d3773911e24 <dde4800d2b0f68b945fd81d4fc2d4a10ae25f743
Siemens · SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPversion=V3.1.5 <*
Siemens · SIMATIC S7-1500 CPU 1518-4 PN/DP MFPversion=V3.1.5 <*

Published CVSS scores

5.5NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
5.5Siemens ProductCERTCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-20Improper Input Validation
T1499Endpoint Denial of Service
T0814Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo