CVE-2021-30278
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 · uneditedImproper input validation in TrustZone memory transfer interface can lead to information disclosure in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, 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 confidenceImproper input validation in the TrustZone memory transfer interface allows a potential attacker to access information beyond intended boundaries. The TrustZone technology creates a secure world and normal world, and the memory transfer interface bridges these domains. Insufficient validation of inputs during memory transfers could enable an information disclosure vulnerability where sensitive data from the secure world may be exposed to the normal world.
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 device chipsetDetermine the specific Qualcomm chip or firmware component used in your device. Check product documentation, device firmware, or system information for the chipset model (Ar8031, Ar8035, Csr8811, Csra6620, Csra6640, Csrb31024, Fsm10055, or Fsm10056).Affected if The device contains any of the listed Qualcomm firmware components.
-
Verify TrustZone is activeCheck whether ARM TrustZone technology is enabled on the device. This may be visible in boot logs, secure boot configuration, or through device-specific diagnostic tools that expose the Trusted Execution Environment (TEE).Affected if TrustZone is active and the device uses one of the affected Qualcomm firmware components.
-
Confirm firmware versionLocate the firmware version information for the specific Qualcomm component. This is typically found in device system settings, boot information, or through manufacturer-provided diagnostic interfaces.Affected if The device firmware version corresponds to any version of the affected Qualcomm components (all versions are vulnerable).
A device is affected if it incorporates any of the listed Qualcomm firmware components (Ar8031, Ar8035, Csr8811, Csra6620, Csra6640, Csrb31024, Fsm10055, Fsm10056) with TrustZone enabled, regardless of version.
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 patches from Qualcomm/affected device manufacturers. This vulnerability resides in the TrustZone firmware and requires a firmware update to remediate; there are no end-user workarounds.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30278 — 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-30278 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