CVE-2025-21074
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 libimagecodec.quram.so prior to SMR Nov-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 · moderate confidenceOut-of-bounds read vulnerability in Samsung's libimagecodec.quram.so image codec library allows remote attackers to access out-of-bounds memory, likely via a specially crafted image file. This memory safety flaw exists in versions prior to the SMR Nov-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.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.
-
Verify Android versionGo to Settings > About Phone > Android version and note the displayed version numberAffected if Version is 13.0, 14.0, 15.0, or 16.0
-
Check Samsung SMR versionGo to Settings > About Phone > Software information and look for the SMR (Samsung Maintenance Release) or firmware date entryAffected if SMR version is earlier than Nov-2025 Release 1 or firmware date is before November 2025
-
Confirm vulnerable library presenceUsing a file manager or ADB, locate libimagecodec.quram.so in /system/lib/ or /vendor/lib/ directoriesAffected if The library exists on the device and the Android version and SMR indicate an unpatched system
-
Identify device modelGo to Settings > About Phone > Model number to confirm it is a Samsung deviceAffected if Device is a Samsung Android phone running an affected version (13.0-16.0) without the November 2025 SMR patch
A Samsung Android device is affected if it runs version 13.0, 14.0, 15.0, or 16.0 and has not received the SMR Nov-2025 Release 1 update, as the vulnerable libimagecodec.quram.so library remains present without the security patch.
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 Nov-2025 Release 1 or later firmware update to all affected devices to remediate the vulnerability. Until patched, avoid processing untrusted image files from unknown sources.
SMR Nov-2025 Release 1 or later
- Navigate to Settings > Software Update on the Samsung Android device
- Check for available updates and ensure the November 2025 security patch (SMR Nov-2025 Release 1) or later is available
- Download and install the latest Samsung security update
- Verify the patch has been applied by checking Settings > About Phone > Software Information > Security patch level
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21074 — 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-21074 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