CVE-2025-20944
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOut-of-bounds read in parsing audio data in libsavsac.so prior to SMR Apr-2025 Release 1 allows local attackers to read out-of-bounds memory.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn out-of-bounds read vulnerability exists in libsavsac.so when parsing audio data. The flaw allows a local attacker to read memory beyond allocated buffer boundaries, potentially exposing sensitive information. This affects Samsung devices running versions prior to the SMR Apr-2025 Release 1.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 13.0= 14.0= 15.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Android versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if Version is 13.0, 14.0, or 15.0
-
Verify libsavsac.so library presenceLocate the file using 'find / -name libsavsac.so 2>/dev/null' via ADB shell, or check common paths like /vendor/lib/ or /system/lib/Affected if The library file exists on the device
-
Check Samsung SMR versionRun 'getprop ro.build.version.samsung' via ADB to retrieve the Samsung Maintenance Release version, or check Settings > About Phone > Software info > Security patch levelAffected if SMR version is earlier than Apr-2025 Release 1 (typically shows as SMR-XXX-2025-04-01 or lower)
-
Confirm audio parsing feature is activeCheck if the device uses Samsung audio processing by reviewing running processes containing 'savsac' via 'ps -A | grep -i savsac' or monitor audio playback activityAffected if The libsavsac.so library is actively loaded or used by system processes
The device is affected if it runs Android 13.0, 14.0, or 15.0, contains the libsavsac.so library, and has an SMR version earlier than Apr-2025 Release 1.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply the Samsung SMR Apr-2025 security update or later to remediate this vulnerability. Organizations should identify devices using the affected library version and prioritize patching based on their exposure model.
SMR Apr-2025 Release 1 or later
- Check for system software updates on your Samsung Galaxy device
- Go to Settings > Software Update > Download and Install
- Ensure the device is updated to SMR Apr-2025 Release 1 or later which contains the fix for CVE-2025-20944
- Verify the security patch level in Settings > About Phone > Software Information shows the April 2025 security update or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20944 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-20944 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data