dbcve.org
AndroidOperating system · Samsung

CVE-2025-20948

HIGH · 7.1 CVSS v3.1 Published 2025-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
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 read in enrollment with cdsp frame secfr trustlet prior to SMR Apr-2025 Release 1 allows local privileged 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

Out-of-bounds read vulnerability in the cdsp frame secfr trustlet (a trusted execution environment component in Qualcomm-based devices) allows local privileged attackers to read out-of-bounds memory prior to the SMR Apr-2025 Release 1 patch.

MitigationApply the SMR Apr-2025 Release 1 security patch or later to remediate the vulnerability in the cdsp frame secfr trustlet; this is a firmware-level update requiring coordination with the device OEM.

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Verify Android version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB
    Affected if The installed version is 13.0, 14.0, or 15.0
  2. Check security patch level
    Go to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADB
    Affected if The patch level is earlier than 2025-04-01 or the SMR Apr-2025 Release 1 has not been applied
  3. Confirm device is Samsung Android
    Verify the device manufacturer is Samsung and the OS is Android; check 'getprop ro.product manufacturer' and 'getprop ro.build.version.release' via ADB
    Affected if The device is not a Samsung Android device (the specific vulnerability affects Samsung implementations)
  4. Identify if cdsp frame secfr trustlet is present
    This is a firmware-level trusted execution environment component in Qualcomm-based devices; checking typically requires root access and inspecting the firmware partition or TEE binaries, which is not directly accessible to standard users
    Affected if The device uses a Qualcomm chipset with TEE and the firmware has not been updated to include the Apr-2025 patch

The device is affected if it is a Samsung Android device running version 13.0, 14.0, or 15.0 with a security patch level earlier than the SMR Apr-2025 Release 1 update.

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 the SMR Apr-2025 Release 1 security patch or later to remediate the vulnerability in the cdsp frame secfr trustlet; this is a firmware-level update requiring coordination with the device OEM.

Recommended fix High confidence

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

  1. Check your Samsung device model and current Android version by navigating to Settings > About Phone > Software Information
  2. Check your current Samsung security patch level by going to Settings > About Phone > Software Information > Security patch level
  3. Locate the SMR (Samsung Mobile Security) Apr-2025 update for your specific device model - this can be done through Settings > Software Update > Download and install, or by checking Samsung's security bulletins at security.samsungmobile.com
  4. Ensure the device is connected to Wi-Fi and has sufficient battery (at least 50%) before initiating the update
  5. Download and install the SMR Apr-2025 security update through the device's software update mechanism
  6. After installation, verify the security patch level shows the April 2025 security update in Settings > About Phone > Software Information
Caveat Standard Samsung security update with no expected breaking changes; as with any system update, ensure backups of critical data exist before applying

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

Fix this in Android Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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