Local kernel-memory disclosure via sensitive log entries
Published Jan 14, 2025 · Updated Jun 9, 2026
Information disclosure in the Windows kernel allows local users with low privileges to read sensitive kernel memory through log files. The kernel writes sensitive memory contents into a log file instead of excluding or redacting them; Microsoft identifies the flaw as CWE-532. Exploitation requires local low-privilege access, and the disclosed data can expose kernel memory without changing data or interrupting service.
Summary
What happened
Information disclosure in the Windows kernel allows local users with low privileges to read sensitive kernel memory through log files. The kernel writes sensitive memory contents into a log file instead of excluding or redacting them; Microsoft identifies the flaw as CWE-532. Exploitation requires local low-privilege access, and the disclosed data can expose kernel memory without changing data or interrupting service.
The record
- CVE
- CVE-2025-21320
- Published
- Jan 14, 2025
- Updated
- Jun 9, 2026
- Vendor
- Microsoft
- Product
- Windows 10 Version 1507
- Classifications
- CWE-532, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 14, 2025CVE publishedPublication date reported by the CVE source.
- Jun 9, 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=10.0.10240.0 <10.0.10240.20890
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