CVE-2021-30338
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 Compute
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 read memory contents beyond intended boundaries, leading to information disclosure. This affects the secure-to-normal world interface in ARM TrustZone technology used by Snapdragon Compute platforms.
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 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 chipset modelCheck the device or system specifications to determine if the chipset is Qualcomm Sd850 or Sdxr1. This may be listed in /proc/cpuinfo, system BIOS/UEFI information, or the device hardware documentation.Affected if The chipset is Qualcomm Sd850 or Sdxr1 - both are affected for all firmware versions.
-
Check TrustZone firmware versionLocate and read the TrustZone (TEE) firmware version. This may be accessible via vendor-specific tools, debug interfaces, or by checking firmware dump files if available. The exact method varies by device manufacturer.Affected if The TrustZone firmware version cannot be determined or is any version of Sd850/Sdxr1 firmware - all versions are affected.
-
Verify TrustZone is enabledCheck if ARM TrustZone is enabled in the system. On supported platforms, this may be visible in boot logs, UEFI/BIOS settings, or via tools like 'arm-none-eabi-readelf' on TEE binaries if accessible.Affected if TrustZone is enabled and the underlying firmware is Sd850 or Sdxr1 - the vulnerable interface is present.
-
Check for secure world interface exposureDetermine if the TrustZone secure-to-normal world interface is accessible or exposed to normal world applications. This typically requires access to TrustZone driver logs, kernel configurations, or vendor diagnostic tools.Affected if The TrustZone memory transfer interface is accessible from the normal world - the vulnerable code path could be triggered.
If the device uses a Qualcomm Sd850 or Sdxr1 chipset with TrustZone enabled, the environment is affected since all firmware versions of these products contain the vulnerability in the TrustZone memory transfer interface.
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 firmware/Software updates provided by the device/OEM manufacturer that address the TrustZone input validation issue. Contact Qualcomm or your device vendor for specific patched versions.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.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 $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30338 — 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-30338 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