CVE-2025-21006
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 write in handling of macro blocks for MPEG4 codec in libsavsvc.so prior to Android 15 allows local attackers to write 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 write vulnerability exists in the MPEG4 codec's macro block handling within libsavsvc.so on Android devices prior to version 15. The flaw allows a local attacker to write memory outside the intended buffer boundaries, potentially leading to code execution or denial of service.
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< 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 OS versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if Version is 14 or lower (anything below 15.0)
-
Locate libsavsvc.so librarySearch for the file using a file manager or via ADB shell command: 'find / -name libsavsvc.so 2>/dev/null'Affected if The library file exists on the device
-
Identify MPEG4 codec usageCheck which apps or processes access libsavsvc.so for MPEG4 decoding. Monitor process activity or review app permissions for media accessAffected if MPEG4 video playback or decoding is performed using the affected library
-
Confirm library version contextCheck the library file properties or metadata if version information is embedded, or correlate with the Samsung Android security patch levelAffected if Running on Samsung Android with security patch level prior to the version 15 update containing the fix
A Samsung Android device is affected if it runs version below 15.0 AND has the libsavsvc.so library present, as the out-of-bounds write flaw in MPEG4 macro block handling can be triggered during video decoding operations.
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 · scoped15.0
Upgrade affected Android devices to version 15 or later to receive the patched libsavsvc.so library.
Android 15.0
- Check the current Android version by navigating to Settings > About Phone > Android version
- Back up all important data to a secure location (cloud storage or local backup)
- Ensure the device is connected to Wi-Fi and has sufficient battery (50% or more)
- Navigate to Settings > System > Software Update (or Settings > Software Update on Samsung devices)
- Check for updates and download any available system updates
- Install the update and restart the device when prompted
- After restart, verify the Android version is 15.0 or higher by checking Settings > About Phone > Android version
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-21006 — 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-21006 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