Memory corruption and disclosure via skipped TLB flushes
Published May 20, 2025 · Updated Sep 8, 2026
Improper input validation in Linux and Siemens SIMATIC and SIPLUS controllers allows local users to corrupt or disclose memory. During an x86 mm switch, should_flush_tlb() incorrectly suppresses the shootdown after load_new_mm_cr3() clears need_flush but before loaded_mm records the new address space. Exploitation requires local low-privileged access and a high-complexity race; stale translations can alter or expose memory and interrupt the affected system.
Summary
What happened
Improper input validation in Linux and Siemens SIMATIC and SIPLUS controllers allows local users to corrupt or disclose memory. During an x86 mm switch, should_flush_tlb() incorrectly suppresses the shootdown after load_new_mm_cr3() clears need_flush but before loaded_mm records the new address space. Exploitation requires local low-privileged access and a high-complexity race; stale translations can alter or expose memory and interrupt the affected system.
The record
- CVE
- CVE-2025-37964
- Published
- May 20, 2025
- Updated
- Sep 8, 2026
- Vendor
- Siemens
- Product
- SIPLUS S7-1500 CPU 1518-4 PN/DP MFP
- Classifications
- CWE-20
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 20, 2025CVE publishedPublication date reported by the CVE source.
- Sep 8, 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.6 <*
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.
Weakness, pattern, technique
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