Memory corruption via softsim trustlet input validation failure
Published Feb 4, 2025 · Updated Mar 25, 2025
Out-of-bounds write in the softsim trustlet on Samsung Mobile Devices allows local privileged attackers to corrupt memory. The trustlet does not properly validate input before a memory write, so the write can extend beyond its allocated boundary. Only select Android 12, 13, and 14 devices before SMR Jan-2025 Release 1 are affected, and exploitation requires local privileged access; Samsung reports memory corruption but not code execution.
Summary
What happened
Out-of-bounds write in the softsim trustlet on Samsung Mobile Devices allows local privileged attackers to corrupt memory. The trustlet does not properly validate input before a memory write, so the write can extend beyond its allocated boundary. Only select Android 12, 13, and 14 devices before SMR Jan-2025 Release 1 are affected, and exploitation requires local privileged access; Samsung reports memory corruption but not code execution.
The record
- CVE
- CVE-2025-20885
- Published
- Feb 4, 2025
- Updated
- Mar 25, 2025
- Vendor
- Samsung Electronics Co., Ltd.
- Product
- Samsung Mobile Devices
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 4, 2025CVE publishedPublication date reported by the CVE source.
- Mar 25, 2025Record 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