Crash-dump hang via unrescheduled vmcore read loop
Published Feb 12, 2025 · Updated May 23, 2026
Improper locking in Linux kernel __read_vmcore allows local users to stall crash-dump collection during kdump processing. The second __read_vmcore loop lacks a guaranteed rescheduling point, which can starve RCU memory reclamation in a constrained kdump image. Local privileges and an active kdump operation are required; the bounded consequence is a stuck crash dump, not data exposure or modification.
Summary
What happened
Improper locking in Linux kernel __read_vmcore allows local users to stall crash-dump collection during kdump processing. The second __read_vmcore loop lacks a guaranteed rescheduling point, which can starve RCU memory reclamation in a constrained kdump image. Local privileges and an active kdump operation are required; the bounded consequence is a stuck crash dump, not data exposure or modification.
The record
- CVE
- CVE-2025-21694
- Published
- Feb 12, 2025
- Updated
- May 23, 2026
- Vendor
- Siemens
- Product
- SIPLUS S7-1500 CPU 1518-4 PN/DP MFP
- Classifications
- CWE-667, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 12, 2025CVE publishedPublication date reported by the CVE source.
- May 23, 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.
- Affected versionversion=V3.1.0 <V3.1.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
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