CVE-2025-58480
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 · uneditedHeap-based buffer overflow in libimagecodec.quram.so prior to SMR Dec-2025 Release 1 allows remote attackers to access 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 confidenceA heap-based buffer overflow vulnerability exists in libimagecodec.quram.so, an image codec library, that allows remote attackers to access out-of-bounds memory prior to the SMR Dec-2025 Release 1. The overflow occurs during image decoding operations, potentially enabling memory corruption or information disclosure.
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.0= 16.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 versionRun 'getprop ro.build.version.release' or check Settings > About Phone > Android version. Confirm it is 13.0, 14.0, 15.0, or 16.0.Affected if Device runs any of the affected Android versions (13.0, 14.0, 15.0, or 16.0)
-
Locate the vulnerable librarySearch for libimagecodec.quram.so on the device using 'find / -name libimagecodec.quram.so 2>/dev/null' or check common paths like /vendor/lib64, /system/lib64, /system/vendor/lib64.Affected if The library exists on the device (indicating the image codec is present)
-
Check library version or build dateUse 'ls -la <path>/libimagecodec.quram.so' to inspect file metadata, or run 'strings <path>/libimagecodec.quram.so | grep -i version' if strings tool is available. Compare the build date to the SMR Dec-2025 Release 1 timeline.Affected if Library build date is prior to December 2025 or version is earlier than the SMR Dec-2025 Release 1 update
-
Identify image decoding usageReview installed applications and system services that process images from remote or untrusted sources (e.g., browsers, messaging apps, image viewers). Use 'ps -A' to list running processes and check which apps have network access.Affected if Applications or services that decode untrusted image content are in use on the device
Device is affected if it runs Samsung Android 13.0-16.0 with a libimagecodec.quram.so version predating the SMR Dec-2025 Release 1 and processes untrusted image content.
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.
From vendor dataApply the SMR Dec-2025 Release 1 or later firmware update to patch the vulnerable libimagecodec.quram.so library. Prioritize updates for systems processing untrusted image content from remote sources.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58480 — 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-58480 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