dbcve.org
AndroidOperating system · Samsung

CVE-2024-20901

HIGH · 7.8 CVSS v3.1 Published 2024-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Improper input validation in copying data to buffer cache in libsaped prior to SMR Jul-2024 Release 1 allows local attackers to write 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 confidence

Improper input validation in libsaped allows local attackers to write out-of-bounds memory when copying data to the buffer cache, likely due to missing bounds checking on input size before a memcpy or similar operation.

MitigationApply the SMR Jul-2024 Release 1 patch to libsaped to address the input validation vulnerability; review and validate all data copy operations in the buffer cache code path for proper bounds checking.

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:= 12.0= 13.0= 14.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
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Check Android version
    Run 'getprop ro.build.version.release' or check Settings > About Phone > Android version
    Affected if Version is 12.0, 13.0, or 14.0 on a Samsung device
  2. Confirm Samsung device
    Run 'getprop ro.product.brand' and verify it returns 'samsung'
    Affected if Device is not a Samsung device (this CVE is Samsung-specific)
  3. Check if libsaped library exists
    Locate libsaped.so in /vendor/lib/ or /system/lib/ directories using 'find / -name libsaped.so 2>/dev/null'
    Affected if libsaped.so is not found on the device
  4. Check Samsung SMR patch level
    Run 'getprop ro.build.version.sem' or 'getprop ro.vendor.build.version.sem' to get the Samsung Maintenance Release version
    Affected if SMR patch level is before Jul-2024 Release 1 (or cannot be determined)
  5. Verify buffer cache operation context
    Review any custom or third-party applications using libsaped for buffer cache operations; check logs for out-of-bounds write errors related to libsaped
    Affected if Applications using libsaped buffer cache features exhibit memory corruption or out-of-bounds write errors

A Samsung Android device on versions 12.0, 13.0, or 14.0 with libsaped present and an SMR patch level before Jul-2024 Release 1 is likely affected by this 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 the SMR Jul-2024 Release 1 patch to libsaped to address the input validation vulnerability; review and validate all data copy operations in the buffer cache code path for proper bounds checking.

Recommended fix High confidence

SMR Jul-2024 Release 1 (or later)

  1. Check your Samsung device model and current Android/SMR version in Settings > About Phone > Software Information
  2. Ensure your device is eligible for the July 2024 SMR (Security Maintenance Release)
  3. Connect device to Wi-Fi and charge to at least 50% battery
  4. Go to Settings > Software Update and tap 'Download and Install'
  5. Wait for the July 2024 SMR update to download and install completely
  6. Alternatively, check with your carrier or Samsung member app for available updates
  7. After update, verify SMR version shows July-2024 or later in Settings > About Phone > Software Information
Caveat Security updates typically have minimal risk; always backup important data before updating as standard practice

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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