dbcve.org
Sm8150 FirmwareOperating system · Qualcomm

CVE-2020-3613

HIGH · 7.8 CVSS v3.1 Published 2020-06-22
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
Double free issue in kernel memory mapping due to lack of memory protection mechanism in Snapdragon Compute, Snapdragon Mobile, Snapdragon Voice & Music in SM8150

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

A double-free vulnerability exists in the kernel memory mapping subsystem of Qualcomm Snapdragon SM8150 chipsets. The lack of proper memory protection mechanisms allows the same memory location to be freed twice, leading to kernel memory corruption that could be exploited for local privilege escalation.

MitigationApply vendor-supplied security patches from Qualcomm and device manufacturers for the SM8150 Snapdragon firmware; this kernel-level issue requires a firmware/microcode update rather than application-level remediation.

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
Sm8150 FirmwareOperating system
Affected:all versions

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. Identify the chipset model
    Check /proc/cpuinfo or device sysfs for processor/hardware identifiers (look for 'SM8150', 'Snapdragon 855', or 'QC SM8150')
    Affected if The device does not contain SM8150 in its hardware identifiers - otherwise all versions are affected
  2. Verify kernel memory mapping subsystem is active
    Confirm the device runs a Linux-based kernel with memory mapping capabilities (检查 /proc/version 或内核模块)
    Affected if Not applicable - this is a kernel subsystem vulnerability present in the firmware itself, not a configurable feature
  3. Confirm firmware version is unpatched
    Check device firmware/modem version via 'getprop' (Android) or 'dmidecode' (if available) - note that ALL SM8150 firmware versions are affected per the CVE
    Affected if Device runs on SM8150 chipset with any firmware version - all versions are vulnerable

If the device uses a Qualcomm Snapdragon SM8150 chipset, it is affected by this vulnerability as all firmware versions contain the double-free flaw in the kernel memory mapping subsystem.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied security patches from Qualcomm and device manufacturers for the SM8150 Snapdragon firmware; this kernel-level issue requires a firmware/microcode update rather than application-level remediation.

Fix this in Sm8150 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing16.0 h
  • Review / QA8.0 h
36.0 hours of engineering $6,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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