CVE-2022-25652
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 issues in BSP due to improper hash verification in 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 confidenceVulnerability in Board Support Package (BSP) firmware for Snapdragon Wired Infrastructure and Networking products where cryptographic hash verification is not properly implemented, potentially allowing integrity bypass of firmware or software components.
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 the installed Qualcomm firmware modelCheck the device or system documentation, boot logs, or firmware image metadata to determine the exact firmware name and version. Common locations: /proc/version, dmesg output, bootloader environment, or vendor management interface.Affected if The firmware matches any of: Csr8811, Ipq5010, Ipq5018, Ipq5028, Ipq6000, Ipq6005, Ipq6010, or Ipq6018
-
Determine the firmware versionRetrieve the firmware version string from the device system information, boot logs, or firmware file properties. Compare against the affected product list.Affected if The installed firmware is any version of the listed Qualcomm products, as all versions are affected
-
Verify cryptographic hash verification implementationInspect the BSP firmware configuration or integrity verification subsystem. Check if hash verification for firmware components is enabled and functioning. This may require access to firmware debug logs, integrity check status, or secure boot configuration.Affected if Cryptographic hash verification is disabled, not implemented, or failing to validate firmware integrity
-
Check secure boot or integrity verification statusExamine the secure boot configuration, signature verification settings, or hash validation mechanisms in the BSP. Look for indicators that firmware integrity checks are present and operational.Affected if Secure boot or firmware integrity verification is not properly configured, is bypassed, or is missing hash validation for firmware components
A user is affected if their system runs any version of the listed Qualcomm firmware (Csr8811, Ipq5010, Ipq5018, Ipq5028, Ipq6000, Ipq6005, Ipq6010, Ipq6018) and the cryptographic hash verification for firmware integrity is not properly implemented or enabled.
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 firmware updates for affected Snapdragon Wired Infrastructure and Networking devices; verify integrity mechanisms are functioning post-update.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25652 — 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-2022-25652 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