dbcve.org
Ar8035 FirmwareOperating system · Qualcomm

CVE-2021-30345

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
RPM secure Stream can access any secure resource due to improper SMMU configuration in Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables, 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 confidence

The vulnerability stems from an improper SMMU (System Memory Management Unit) configuration in Qualcomm Snapdragon chips that allows the RPM (Resource Power Manager) secure stream to bypass intended memory isolation boundaries and access any secure resource on the system. This is a hardware/firmware-level flaw affecting the RPM secure stream component.

MitigationApply firmware updates from device manufacturers (Qualcomm and downstream OEMs) that address the SMMU configuration. For unpatchable devices, implement network segmentation and restrict physical access to limit exploitation vectors.

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
Ar8035 FirmwareOperating system
Affected:all versions
Qca9984 FirmwareOperating system
Affected:all versions
Qcm2290 FirmwareOperating system
Affected:all versions
Qcm4290 FirmwareOperating system
Affected:all versions
Qcs2290 FirmwareOperating system
Affected:all versions
Qcs405 FirmwareOperating system
Affected:all versions
Qcs4290 FirmwareOperating system
Affected:all versions
Sd460 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 Qualcomm chip model in your device
    Check device documentation, system information, or hardware specs to determine the specific Qualcomm Snapdragon or Qualcomm Atheros chip model (e.g., Qca9984, Qcm2290, Qcm4290, Qcs2290, Qcs405, Qcs4290, Sd460, Ar8035)
    Affected if The chip model matches any of the listed affected products: Qca9984, Qcm2290, Qcm4290, Qcs2290, Qcs405, Qcs4290, Sd460, or Ar8035
  2. Determine the firmware version of the affected Qualcomm component
    Access the device's firmware or bootloader interface, or use vendor-specific diagnostic tools to retrieve the firmware version for the specific Qualcomm chip identified
    Affected if The firmware version can be retrieved and confirmed to be running on an affected Qualcomm component
  3. Verify if the device uses SMMU (System Memory Management Unit) with RPM secure stream
    Consult the device hardware specification or firmware documentation to confirm whether the Qualcomm chip implements SMMU and utilizes the RPM (Resource Power Manager) secure stream functionality
    Affected if The device implements SMMU with RPM secure stream on an affected Qualcomm chip (this is the default configuration for the listed affected products)
  4. Check for available firmware updates from the device manufacturer
    Contact the device OEM or check the manufacturer's support website for any available firmware updates for the specific Qualcomm component
    Affected if No firmware update has been applied and the device runs on an affected Qualcomm firmware (all versions listed are affected)

A user is affected if their device contains any of the listed Qualcomm chips (Qca9984, Qcm2290, Qcm4290, Qcs2290, Qcs405, Qcs4290, Sd460, Ar8035) with their firmware, since all versions of these components contain the SMMU misconfiguration allowing RPM secure stream to bypass memory isolation.

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 firmware updates from device manufacturers (Qualcomm and downstream OEMs) that address the SMMU configuration. For unpatchable devices, implement network segmentation and restrict physical access to limit exploitation vectors.

Fix this in Ar8035 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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