CVE-2021-35109
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 · uneditedPossible address manipulation from APP-NS while APP-S is configuring an RG where it tries to merge the address ranges in Snapdragon Connectivity, 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 confidenceThis is a TrustZone vulnerability in Qualcomm Snapdragon chips where the non-secure world (APP-NS) can manipulate addresses while the secure world (APP-S) is configuring a Resource Group (RG) during address range merging operations. The issue allows a potential attacker in the non-secure domain to influence memory address handling in the secure domain.
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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Qualcomm chipset modelCheck device specifications, AT command output (at+cgmm or at+qcfg), or system info for the baseband processor model. Common locations: Settings > About Phone > Baseband, or via terminal with 'getprop ro.board.platform' or 'cat /proc/cpuinfo'Affected if The chipset matches one of: Sd 8 Gen1 5g, Sm7450, Sm8475, Sm8475p, Wcd9370, Wcd9375, Wcd9380, or Wcd9385
-
Check TrustZone/secure world statusVerify that TrustZone is enabled and operational on the device. This is typically default on affected chips but can be checked via security certification status or by examining if secure elements (like DRM, biometric storage) are functioningAffected if TrustZone is active (default state for all affected chips)
-
Check firmware version if accessibleAttempt to retrieve firmware version via: AT commands (at+cgmr for baseband), Settings > About Phone > Modem/Firmware version, or via 'getprop' commands (getprop gsm.version.baseband, getprop ro.build.version.security_patch)Affected if Firmware is present on affected chipset models - all versions of the listed firmware are affected
If your device uses any of the listed Qualcomm chipsets (Sd 8 Gen1 5g, Sm7450, Sm8475, Sm8475p, Wcd9370, Wcd9375, Wcd9380, Wcd9385), your TrustZone implementation is likely vulnerable since all firmware versions are affected.
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 for Snapdragon Connectivity and Snapdragon Mobile devices. This is a hardware/firmware-level fix that requires patching from the OEM using Qualcomm's security bulletins.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-35109 — 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-35109 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