CVE-2025-21422
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 · uneditedCryptographic issue while processing crypto API calls, missing checks may lead to corrupted key usage or IV reuses.
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 cryptographic vulnerability in crypto API processing where missing validation checks can lead to corrupted key usage or Initialization Vector (IV) reuse. IV reuse in particular can severely compromise confidentiality in symmetric encryption modes like CBC, potentially allowing cryptanalysis of encrypted data.
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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 affected Qualcomm firmwareInventory your devices or systems for the following firmware: Qualcomm Aqt1000, Ar8035, Fastconnect 6200/6700/6800/6900/7800, or Qam8255p. Check device documentation, firmware images, or system information for these components.Affected if Any of these firmware components are present in your environment.
-
Determine firmware versionUse vendor-provided tools or commands to retrieve the installed firmware version for any identified Qualcomm component. Compare against the affected product list.Affected if The firmware version corresponds to any of the listed affected products (all versions are affected).
-
Check for crypto API usageReview your application code, system configuration, or firmware to determine if the Qualcomm crypto API is being called. Look for references to cryptographic functions, symmetric encryption, or key handling routines.Affected if Your code or configuration makes calls to the Qualcomm crypto API.
-
Identify symmetric encryption modeInspect encryption configurations to determine if CBC (Cipher Block Chaining) mode or other symmetric encryption modes that require unique Initialization Vectors are in use. Check configuration files, API calls, or documentation.Affected if CBC mode or similar IV-dependent symmetric encryption is enabled or configured.
-
Review IV generation implementationExamine how Initialization Vectors are generated for cryptographic operations. Look for custom IV generation code, hardcoded IV values, or non-random IV patterns in your codebase or configuration.Affected if IVs are generated manually, hardcoded, or use predictable patterns rather than cryptographically secure random generation.
You are affected if your environment contains any of the listed Qualcomm firmware products and uses the crypto API with symmetric encryption modes where IV handling may occur.
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-provided security patches for the affected cryptographic library or API. If no patch is available, review all cryptographic key handling and IV generation code to ensure proper randomness and uniqueness requirements are met.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21422 — 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-2025-21422 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