CVE-2020-3664
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 · uneditedOut of bound read access in hypervisor due to an invalid read access attempt by passing invalid addresses in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking
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 confidenceOut-of-bounds read vulnerability in the hypervisor component of Qualcomm Snapdragon chips. The issue occurs when invalid addresses are passed to the hypervisor, allowing unauthorized memory reads outside intended boundaries.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/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 installed Qualcomm firmware productsExamine the device firmware or system information to determine which Qualcomm firmware components are present. For embedded devices, this may require accessing /proc, /sys, bootloader info, or device management interfaces. Look for modules or firmware files matching Aqt1000, Ar8031, Ar8035, Csr8811, Csra6620, Csra6640, Csrb31024, or Fsm10055.Affected if Any of the listed Qualcomm firmware products (Aqt1000, Ar8031, Ar8035, Csr8811, Csra6620, Csra6640, Csrb31024, Fsm10055) are present on the device, regardless of version, since all versions are affected.
-
Verify hypervisor component statusDetermine whether the Qualcomm hypervisor component is active or accessible on the system. This may involve checking running processes, loaded kernel modules, or hypervisor-specific status registers. Consult device-specific documentation for hypervisor status indicators.Affected if The Qualcomm hypervisor component is enabled and accessible on the system, as this is required for the out-of-bounds read to occur.
-
Check for abnormal memory access patternsReview system logs, hypervisor logs, or memory access audit trails for evidence of unauthorized memory read attempts using invalid addresses. Look for error messages related to out-of-bounds memory access, memory protection faults, or hypervisor errors involving address validation failures.Affected if Logs or audit records show memory read operations that attempted to access addresses outside intended boundaries through the hypervisor, which would indicate active exploitation or attempted exploitation of this vulnerability.
A system is affected if it contains any of the listed Qualcomm firmware products (Aqt1000, Ar8031, Ar8035, Csr8811, Csra6620, Csra6640, Csrb31024, Fsm10055) with the hypervisor component enabled, since all versions of these products contain the vulnerability.
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 firmware/hypervisor updates from Qualcomm and device manufacturers. This is a firmware-level fix that must be distributed through device update mechanisms.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3664 — 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-3664 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