CVE-2021-35070
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 · uneditedRPM secure Stream can access any secure resource due to improper SMMU configuration and can lead to information disclosure in Snapdragon Industrial IOT, Snapdragon Mobile
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 confidenceImproper SMMU (System Memory Management Unit) configuration in Qualcomm Snapdragon chips allows the RPM (Runtime Power Management) secure stream to bypass memory isolation and access any secure resource, leading to information disclosure. The SMMU normally enforces DMA protection and device isolation, but the misconfiguration defeats this security boundary.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Qualcomm chip model in the deviceUse system information commands (e.g., `lspci`, `lsusb`, `cat /proc/cpuinfo`, or vendor-specific tools) to determine the exact Qualcomm chip present in the systemAffected if The identified chip model matches Qcm6125, Qcs6125, Sd665, Wcd9370, Wcd9375, Wcn3950, Wcn3980, or Wsa8810
-
Determine the firmware version of the affected Qualcomm componentQuery the firmware version through vendor-specific diagnostic tools, debug interfaces, or system logs that report chip firmware informationAffected if The firmware version corresponds to any version of the affected chips (all versions are impacted)
-
Verify the SMMU configuration for the RPM secure streamExamine SMMU (System Memory Management Unit) configuration registers and IOMMU settings through low-level hardware debugging or firmware analysis tools to check if the RPM stream has unrestricted accessAffected if The SMMU configuration shows the RPM secure stream bypasses memory isolation protections or has access to secure resources it should not have
-
Check for DMA protection enforcement on affected devicesReview DMA protection settings and device isolation configurations in the firmware or boot logs to verify the SMMU is properly enforcing these security boundariesAffected if DMA protection is not enforced or device isolation is weakened due to improper SMMU configuration
The device is affected if it contains any of the listed Qualcomm chips (Qcm6125, Qcs6125, Sd665, Wcd9370, Wcd9375, Wcn3950, Wcn3980, Wsa8810) with firmware that has the improper SMMU configuration allowing the RPM stream to bypass memory isolation.
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 updates from Qualcomm for affected Snapdragon Industrial IOT and Mobile chipsets; coordinate with device manufacturers for OTA patch deployment.
- Consultation8.0 h
- Implementation16.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 $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-35070 — 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-2021-35070 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