dbcve.org
Kamorta FirmwareOperating system · Qualcomm

CVE-2020-3636

HIGH · 7.8 CVSS v3.1 Published 2020-09-08
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
u'Out of bound writes happen when accessing usage_table header entry beyond the memory allocated for the header' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking in Kamorta, QCS404, QCS610, Rennell, SC7180, SDX55, SM6150, SM7150, SM8250, 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 confidence

Out-of-bounds write vulnerability in Qualcomm Snapdragon chipsets where accessing usage_table header entries exceeds allocated memory boundaries. This memory corruption issue could allow privilege escalation or denial of service. The vulnerability exists in the Snapdragon Auto, Compute, Consumer IOT, Mobile, and Wired Infrastructure product lines.

MitigationApply vendor-supplied firmware/microcode security patches from Qualcomm through downstream device manufacturers (OEMs/ODMs). This is a hardware/firmware-level issue requiring updates to the chipset firmware, not a software patch.

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
Kamorta FirmwareOperating system
Affected:all versions
Qcs404 FirmwareOperating system
Affected:all versions
Qcs610 FirmwareOperating system
Affected:all versions
Rennell FirmwareOperating system
Affected:all versions
Sc7180 FirmwareOperating system
Affected:all versions
Sdx55 FirmwareOperating system
Affected:all versions
Sm6150 FirmwareOperating system
Affected:all versions
Sm7150 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 Qualcomm chipset model in your device
    Check system information, device specifications, or bootloader logs to determine the exact Snapdragon chipset variant (e.g., via 'cat /proc/cpuinfo' on Linux, or check BIOS/UEFI diagnostics on embedded systems)
    Affected if The chipset model matches Kamorta, Qcs404, Qcs610, Rennell, Sc7180, Sdx55, Sm6150, or Sm7150
  2. Locate the usage_table firmware component
    Access the firmware image or debug interface provided by the device OEM to inspect the chipset firmware structure; look for the usage_table module in the firmware binary
    Affected if The usage_table header entries exist in the firmware, indicating the vulnerable component is present
  3. Verify the firmware version
    Retrieve the firmware version string from the chipset (via manufacturer tools, debug UART, or OEM-provided diagnostic software) and compare against the affected product list
    Affected if The firmware version corresponds to any of the listed affected products (all versions of Kamorta, Qcs404, Qcs610, Rennell, Sc7180, Sdx55, Sm6150, Sm7150)
  4. Confirm the usage_table boundary condition
    If firmware debugging is available, examine memory allocation for usage_table headers and verify whether header access can exceed the allocated buffer size during normal operation
    Affected if The firmware allows access to usage_table header entries beyond allocated memory boundaries

If your device contains any of the listed Qualcomm Snapdragon chipset models (Kamorta, Qcs404, Qcs610, Rennell, Sc7180, Sdx55, Sm6150, Sm7150) with the usage_table firmware component present, you are affected since all firmware versions of these products contain the 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.

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

Apply vendor-supplied firmware/microcode security patches from Qualcomm through downstream device manufacturers (OEMs/ODMs). This is a hardware/firmware-level issue requiring updates to the chipset firmware, not a software patch.

Fix this in Kamorta Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA6.0 h
40.0 hours of engineering $6,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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