dbcve.org
Qcm2290 FirmwareOperating system · Qualcomm

CVE-2021-35080

MEDIUM · 5.5 CVSS v3.1 Published 2022-06-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
Disabled SMMU from secure side while RPM is assigned a secure stream can lead to information disclosure in Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

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 vulnerability in Qualcomm Snapdragon chipsets allows information disclosure when the SMMU (System Memory Management Unit) is disabled from the secure world while RPM (Remote Processor Manager) is assigned a secure stream. This could expose sensitive data from the secure execution environment to non-secure contexts.

MitigationApply firmware updates provided by Qualcomm/OEM vendors that address this SMMU configuration issue in the secure boot chain. Verify that secure streams maintain proper SMMU protection even during power management transitions.

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
Qcm2290 FirmwareOperating system
Affected:all versions
Qcm4290 FirmwareOperating system
Affected:all versions
Qcs2290 FirmwareOperating system
Affected:all versions
Qcs4290 FirmwareOperating system
Affected:all versions
Sd460 FirmwareOperating system
Affected:all versions
Sd480 FirmwareOperating system
Affected:all versions
Sd662 FirmwareOperating system
Affected:all versions
Sd680 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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 the processor/chipset information on the device or in system documentation (e.g., /proc/cpuinfo on Android, or dmesg output). Look for model numbers such as Qcm2290, Qcm4290, Qcs2290, Qcs4290, Sd460, Sd480, Sd662, or Sd680.
    Affected if The chipset matches one of the listed affected models (Qcm2290, Qcm4290, Qcs2290, Qcs4290, Sd460, Sd480, Sd662, Sd680).
  2. Check firmware version
    Query the firmware version through vendor-specific tools, bootloader access, or by inspecting the firmware image if accessible. On Android, try 'getprop' or check /vendor/firmware/ directory for version indicators.
    Affected if The device runs on an affected chipset and the firmware version cannot be determined or is prior to a security patch addressing this issue.
  3. Inspect SMMU configuration in secure world
    Analyze the TrustZone firmware or tee binary (if accessible) for SMMU configuration code. Look for code paths where SMMU is disabled or not initialized while secure streams are being set up. Use firmware binary analysis tools to search for SMMU-related registers and stream ID configurations.
    Affected if The firmware analysis reveals SMMU is disabled or misconfigured in the secure world context while RPM is assigned a secure stream ID.
  4. Check RPM stream assignments
    Examine the RPM (Remote Processor Manager) configuration in the firmware. Look for stream ID assignments to RPM and verify whether proper SMMU protection is enforced. Search for stream configuration data structures in the firmware binary.
    Affected if RPM is assigned a secure stream without SMMU protection enabled, leaving secure memory accessible to non-secure contexts.

A device is affected if it uses any of the listed Qualcomm chipsets (Qcm2290, Qcm4290, Qcs2290, Qcs4290, Sd460, Sd480, Sd662, Sd680) and the firmware has not been patched to enforce proper SMMU protection for secure streams assigned to RPM.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply firmware updates provided by Qualcomm/OEM vendors that address this SMMU configuration issue in the secure boot chain. Verify that secure streams maintain proper SMMU protection even during power management transitions.

Recommended fix Moderate confidence

Firmware update from Qualcomm/OEM containing the CVE-2021-35080 fix (specific version number not provided in reference material)

  1. Contact the device manufacturer (OEM) to obtain firmware updates that address CVE-2021-35080
  2. Request the specific SMMU security fix for the affected Snapdragon chipset (Qcm2290, Qcm4290, Qcs2290, Qcs4290, Sd460, Sd480, Sd662, or Sd680)
  3. Apply the Qualcomm firmware update provided by the OEM following their standard firmware upgrade procedure
  4. Verify the SMMU is properly enabled in secure mode after the update
Caveat Firmware updates may require device downtime and should be tested in a staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Qcm2290 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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