dbcve.org
AndroidOperating system · Samsung

CVE-2025-21075

HIGH · 7.5 CVSS v3.1 Published 2025-11-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Out-of-bounds write 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 confidence

An out-of-bounds write vulnerability exists in Samsung's libimagecodec.quram.so image processing library prior to the November 2025 Security Maintenance Release (SMR Nov-2025 Release 1). The flaw allows remote attackers to access out-of-bounds memory by processing specially crafted image files, potentially leading to arbitrary code execution or information disclosure.

MitigationApply Samsung's SMR Nov-2025 Release 1 or later security update which patches the vulnerable libimagecodec.quram.so library. Users should avoid processing untrusted image files until the device is updated.

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
AndroidOperating system
Affected:= 13.0= 14.0= 15.0= 16.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Android OS version
    Go to Settings > About Phone > Android version. Verify if the version is 13.0, 14.0, 15.0, or 16.0.
    Affected if The device runs Android 13.0, 14.0, 15.0, or 16.0 and has not received the November 2025 security update.
  2. Check Samsung Security Patch Level
    Go to Settings > About Phone > Software information > Build number. Tap Build number 7 times to enable developer options, then go to Settings > System > Developer options > Samsung Patch SDK. Verify the Security software version.
    Affected if The Security Patch Level is earlier than November 2025.
  3. Verify libimagecodec.quram.so library presence
    Using ADB or a file manager with root access, check for the presence of libimagecodec.quram.so in /system/lib/ or /vendor/lib/ directories.
    Affected if The vulnerable library exists on the device without the November 2025 patch.
  4. Confirm SMR update status
    Check Settings > Software update > Download and install. Ensure the device has pulled and installed the November 2025 Security Maintenance Release (SMR Nov-2025 Release 1).
    Affected if The device has not installed the November 2025 SMR update.

A user is affected if their Samsung Android device runs version 13.0, 14.0, 15.0, or 16.0 and lacks the November 2025 security update containing the patched libimagecodec.quram.so library.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Samsung's SMR Nov-2025 Release 1 or later security update which patches the vulnerable libimagecodec.quram.so library. Users should avoid processing untrusted image files until the device is updated.

Recommended fix Moderate confidence

SMR Nov-2025 Release 1 (Samsung Mobile Security Patch)

  1. Check your Samsung device model for SMR Nov-2025 Release 1 availability in the Samsung Security Bulletin (security.samsungmobile.com)
  2. Navigate to Settings > Security and privacy > Security update on your Samsung Android device
  3. Ensure the device is connected to Wi-Fi and charged
  4. Tap 'Check for updates' and wait for the November 2025 security patch to appear
  5. If available, download and install the SMR Nov-2025 Release 1 security update
  6. After installation, verify the Security patch level shows November 2025 in Settings > Security and privacy > Security update
Caveat Security patches are cumulative; applying this patch should not introduce functional breaking changes but does require device reboot

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-21075 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-21075 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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