dbcve.org
AndroidOperating system · Samsung

CVE-2025-20992

HIGH · 7.7 CVSS v3.1 Published 2025-06-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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-bound read in libsecimaging.camera.samsung.so prior to SMR Feb-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 · moderate confidence

An out-of-bounds read vulnerability in libsecimaging.camera.samsung.so (Samsung camera imaging library) prior to SMR Feb-2025 Release 1 allows local attackers to read memory outside allocated buffers. This memory safety flaw in the camera library could expose sensitive data or aid in further exploitation on affected Samsung devices.

MitigationApply Samsung's SMR Feb-2025 Release 1 security update or later firmware versions to devices running the affected camera library.

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

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
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/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 checks

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

  1. Confirm device is Samsung Android
    Check device manufacturer and model via Settings > About Phone > Manufacturer should show 'Samsung'
    Affected if Device is not a Samsung Android device - different vendors use different camera libraries and are not affected by this specific vulnerability
  2. Check Android version
    Navigate to Settings > About Phone > Android version. Affected versions are exactly 13.0, 14.0, or 15.0
    Affected if Android version is 13.0, 14.0, or 15.0 - these are the only affected versions per the CVE. Versions below 13.0 or above 15.0 are not listed as affected
  3. Locate the vulnerable camera library
    Using a file explorer with root access or ADB shell, search for 'libsecimaging.camera.samsung.so' in /system/lib or /vendor/lib directories
    Affected if The library file libsecimaging.camera.samsung.so exists on the device - its presence is required for the vulnerability to apply
  4. Check firmware build date
    Navigate to Settings > About Phone > Software Information > Build number. The SMR Feb-2025 Release 1 patch should have a build date on or after February 2025
    Affected if Build date is before February 2025 or the device shows no February 2025 security patch level - the vulnerability exists in unpatched firmware

A Samsung Android device on version 13.0, 14.0, or 15.0 with the libsecimaging.camera.samsung.so library present and no February 2025 security update is likely affected by this out-of-bounds read vulnerability.

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 Feb-2025 Release 1 security update or later firmware versions to devices running the affected camera library.

Recommended fix High confidence

SMR Feb-2025 Release 1 (February 2025 Samsung Security Patch)

  1. Check the current Android security patch level on the device by going to Settings > About Phone > Security Patch Level
  2. Verify that SMR Feb-2025 Release 1 (February 2025 security update) is available for the specific Samsung device model
  3. If the update is available, download and install the February 2025 security patch through Settings > System Update > Check for Updates
  4. After installation, confirm the Security Patch Level reflects February 2025 or later

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20992 — 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-20992 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