Memory corruption via invalid initialization input
Published May 7, 2025 · Updated May 7, 2025
Out-of-bounds write in libsavsvc.so on Samsung Mobile Devices running Android 13, 14, or 15 allows local users to corrupt memory. During memory initialization, the library accepts improperly validated input and writes beyond the intended memory boundary. Exploitation requires local access and user interaction; the documented consequence is out-of-bounds memory modification, not a separately confirmed code-execution outcome.
Summary
What happened
Out-of-bounds write in libsavsvc.so on Samsung Mobile Devices running Android 13, 14, or 15 allows local users to corrupt memory. During memory initialization, the library accepts improperly validated input and writes beyond the intended memory boundary. Exploitation requires local access and user interaction; the documented consequence is out-of-bounds memory modification, not a separately confirmed code-execution outcome.
The record
- CVE
- CVE-2025-20963
- Published
- May 7, 2025
- Updated
- May 7, 2025
- Vendor
- Samsung Electronics Co., Ltd.
- Product
- Samsung Mobile Devices
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 7, 2025CVE publishedPublication date reported by the CVE source.
- May 7, 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