CVE-2020-3676
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 · uneditedPossible memory corruption in perfservice due to improper validation array length taken from user application. in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in APQ8096AU, APQ8098, Kamorta, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8998, Nicobar, QCM2150, QCS605, QM215, Rennell, Saipan, SDM429, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SM6150, SM7150, SM8150, SM8250, SXR1130, SXR2130
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 confidenceMemory corruption vulnerability in Qualcomm's perfservice where array length values passed from user applications are not properly validated before use, allowing a malicious local application to trigger buffer overflow conditions and potentially escalate privileges.
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 versionsall versionsall versionsall versionsall versionsall versionsall versionsall 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Qualcomm chipset modelCheck the device specifications or use commands like 'cat /proc/cpuinfo' on Android, or check 'Settings > About Phone > Model' to identify the chipset (e.g., Apq8096au, Apq8098, Kamorta, Msm8917, Msm8920, Msm8937, Msm8940, Msm8953)Affected if The device uses any of the following chipsets: Apq8096au, Apq8098, Kamorta, Msm8917, Msm8920, Msm8937, Msm8940, or Msm8953
-
Check the firmware versionCheck the firmware or build version in device settings (usually under 'Settings > About Phone > Build Number' or 'Settings > System > Firmware Version') and compare against any available patch information from the device OEMAffected if Firmware is an unpatched version - all versions of the listed chipsets are affected until OEM applies the fix
-
Verify Android security patch levelCheck the Android security patch level in 'Settings > About Phone > Security Patch Level' - this indicates when the last security update was appliedAffected if Security patch level is earlier than the month/year when the fix for this CVE was released by the device OEM
-
Confirm perfservice availabilityCheck if the perfservice ( Qualcomm Performance Service) is present and accessible on the device - this can be done via 'dumpsys' command on Android or reviewing installed system servicesAffected if perfservice is exposed and running, allowing a local application to interact with it
A device is affected if it uses any of the listed Qualcomm chipsets (Apq8096au, Apq8098, Kamorta, Msm8917, Msm8920, Msm8937, Msm8940, or Msm8953) and has not received the vendor firmware/security patch that addresses this improper array validation in perfservice.
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-provided firmware/security patch updates from device OEMs that include the fix for this improper array validation in perfservice. Until patched, limit application permissions and avoid installing apps from untrusted sources.
- Consultation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,048.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3676 — 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-3676 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