CVE-2020-0252
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 · uneditedThere is a possible memory corruption due to a use after free.Product: AndroidVersions: Android SoCAndroid ID: A-152236803
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 confidenceA use-after-free vulnerability in the Android SoC (System-on-Chip) subsystem allows memory corruption. The vulnerability occurs when memory is accessed after it has been freed, potentially enabling arbitrary code execution or denial of service.
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 dataall versionsCVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify your device SoC modelRun 'cat /proc/cpuinfo' or check device settings under 'About Phone' > 'Processor' or 'SoC' to find the chipset manufacturer and model (e.g., Qualcomm Snapdragon, MediaTek Helio, Samsung Exynos)Affected if The device uses any SoC - this vulnerability affects all Android SoC subsystems
-
Locate the SoC firmware versionCheck /sys/firmware/devicetree/base/model or use 'getprop ro.hardware' and 'getprop ro.board.platform' to identify the specific SoC revisionAffected if The device has an unpatched SoC firmware version
-
Verify the Android kernel versionRun 'uname -r' or check 'getprop ro.kernel.version' to document the kernel version in useAffected if The kernel interacts directly with the vulnerable SoC subsystem drivers
-
Check vendor security bulletinReview your device manufacturer's security update bulletin for CVE-2020-0252 - look for 'SoC' or 'use-after-free' references in the patch notesAffected if Your device security update does not include a fix for this CVE
-
Confirm SoC driver is loadedVerify the SoC subsystem is active by checking 'lsmod' for loaded kernel modules related to your SoC (e.g., qcom, mtk, exynos modules)Affected if The SoC hardware and its drivers are present and operational on the device
You are affected if your Android device has not received a vendor-supplied patch for CVE-2020-0252 in the SoC subsystem, as all Android versions are impacted regardless of the SoC manufacturer.
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.
From vendor dataApply vendor-supplied patches for Android SoC components; due to the supply chain complexity, contact your device/SoC vendor for specific patch availability and deployment timelines.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
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 locallyCheck whether your project pulls in CVE-2020-0252 — 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-2020-0252 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