CVE-2021-1935
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 null pointer dereference due to lack of validation check for passed pointer during key import in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Voice & Music, Snapdragon Wearables
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 · high confidenceA null pointer dereference vulnerability exists in the key import functionality of Qualcomm Snapdragon chipsets due to insufficient validation of a pointer before use. An attacker could exploit this by providing a NULL pointer during key import operations, potentially causing a denial of service or enabling further exploitation.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 chipset modelCheck the device hardware specifications or system information to determine the Qualcomm Snapdragon or other Qualcomm chipset model (e.g., Apq8009, Apq8017, Apq8037, Apq8053, Apq8064au, Apq8096au, Aqt1000, Ar8031).Affected if The device uses any of the following chipsets: Apq8009, Apq8017, Apq8037, Apq8053, Apq8064au, Apq8096au, Aqt1000, or Ar8031.
-
Verify firmware versionRetrieve the firmware version information from the device settings, system diagnostics, or by querying /proc/version or similar system files. Compare against available patch information from the device manufacturer.Affected if The device firmware is any version on an affected chipset (all versions are impacted).
-
Check if key import functionality is in useReview application logs, security configuration settings, or system behavior to determine whether key import operations (importing cryptographic keys into secure hardware) are performed on the device.Affected if Key import operations are performed on the device using the affected chipset firmware.
-
Audit key import code pathsIf you have access to the firmware or application code, search for calls to key import APIs or functions that handle importing cryptographic keys into hardware security modules.Affected if The codebase contains key import functionality running on an affected chipset.
The environment is affected if the device uses any of the listed Qualcomm chipsets (Apq8009, Apq8017, Apq8037, Apq8053, Apq8064au, Aqt1000, or Ar8031) and performs key import operations, regardless of firmware 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 for affected Snapdragon chipset families. Device manufacturers must integrate the patched firmware into their products.
- Consultation8.0 h
- Implementation4.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 $8,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1935 — 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-1935 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