Privileged memory corruption via unvalidated Keymaster trustlet input
Published May 7, 2025 · Updated Feb 26, 2026
Out-of-bounds write in Keymaster trustlet on Samsung Mobile Devices before SMR May-2025 Release 1 allows local privileged attackers to corrupt memory. The trustlet fails to validate attacker-controlled input before a memory write, allowing the write to exceed its intended bounds. Exploitation requires local high privileges on an affected Android 13, 14, or 15 device; Samsung reports no more specific consequence than out-of-bounds memory modification.
Summary
What happened
Out-of-bounds write in Keymaster trustlet on Samsung Mobile Devices before SMR May-2025 Release 1 allows local privileged attackers to corrupt memory. The trustlet fails to validate attacker-controlled input before a memory write, allowing the write to exceed its intended bounds. Exploitation requires local high privileges on an affected Android 13, 14, or 15 device; Samsung reports no more specific consequence than out-of-bounds memory modification.
The record
- CVE
- CVE-2025-20937
- Published
- May 7, 2025
- Updated
- Feb 26, 2026
- Vendor
- Samsung Electronics Co., Ltd.
- Product
- Samsung Mobile Devices
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 7, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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