CVE-2021-35097
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 authentication bypass due to improper order of signature verification and hashing in the signature verification call in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, 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 · moderate confidenceAuthentication bypass vulnerability in Qualcomm Snapdragon chipsets caused by improper ordering of signature verification and hashing operations. This allows attackers to potentially bypass cryptographic signature checks by manipulating the verification sequence.
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 installed Qualcomm chipset modelCheck system documentation, device inventory, or use hardware inspection commands (such as 'lspci', 'lsusb', or manufacturer-provided diagnostic tools) to identify the specific Qualcomm chipset model present in the systemAffected if The chipset model matches any of the following: Aqt1000, Ar8031, Ar8035, Csra6620, Csra6640, Csrb31024, Mdm9150, or Qca6174a firmware
-
Retrieve firmware version of the Qualcomm chipsetUse vendor-specific tools, boot logs, or firmware dump utilities to extract and examine the currently installed firmware version of the identified Qualcomm chipsetAffected if The firmware version cannot be determined, or the device uses any version of the listed affected firmware (all versions are impacted)
-
Verify if secure boot or signature verification is enabledCheck the device security configuration settings, boot chain configuration, or EFI/bootloader logs to determine whether cryptographic signature verification for firmware or boot processes is currently enabledAffected if Signature verification is enabled on a device containing any of the affected Qualcomm chipsets listed above
-
Examine boot chain integrity logsReview system boot logs, TEE (Trusted Execution Environment) logs, or secure boot audit logs for any warnings related to signature verification failures, hash mismatches, or verification ordering anomaliesAffected if Logs indicate signature verification is occurring but with inconsistent ordering, or if verification can be bypassed through manipulation of the verification sequence
A system is affected if it contains any of the listed Qualcomm chipset firmware (Aqt1000, Ar8031, Ar8035, Csra6620, Csra6640, Csrb31024, Mdm9150, or Qca6174a) and has signature verification or secure boot enabled, since the vulnerability allows bypassing cryptographic signature checks through manipulation of the verification sequence.
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 firmware updates from device manufacturers that include the Qualcomm fix. Contact device vendors for specific patch availability and deployment timelines.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-35097 — 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-35097 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