CVE-2022-25702
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 · uneditedDenial of service in modem due to reachable assertion while processing reconfiguration message in Snapdragon Auto, Snapdragon Compute, Snapdragon Industrial IOT, Snapdragon Mobile, 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 confidenceA denial of service vulnerability exists in Qualcomm Snapdragon modem firmware where an assertion is triggered when processing specially crafted reconfiguration messages. The reachable assertion causes the modem to crash or become unavailable, resulting in a DoS condition.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 Qualcomm chipset model in your deviceCheck device specifications, system information, or modem diagnostic data to determine the exact Qualcomm chipset (e.g., Apq8009, Apq8017, Apq8037, Aqt1000, Ar8035, Fsm10055, Msm8108, Msm8208). This may be listed in the device datasheet, baseband information, or through AT commands like 'AT+CGMM' or 'AT+QCFG' on some modems.Affected if The chipset matches any of the following: Apq8009, Apq8017, Apq8037, Aqt1000, Ar8035, Fsm10055, Msm8108, or Msm8208
-
Confirm the device uses a cellular modem based on affected Snapdragon firmwareVerify that your device contains a cellular modem subsystem built on the listed Qualcomm platform. Check product documentation, FCC filings, or device teardowns for the modem chipset designation.Affected if The device incorporates any of the listed Qualcomm firmware platforms as its cellular modem processor
-
Check if the modem firmware version is accessible for verificationAttempt to retrieve the modem firmware version through device diagnostics, manufacturer APIs, AT command interface (e.g., 'AT+CGMR', 'AT+QVER'), or system logs. Not all devices expose this information to end users.Affected if Firmware version information is obtainable (for confirmation purposes, though all versions of affected products are vulnerable)
-
Determine if the device processes reconfiguration messagesThis is inherent to normal modem operation. The vulnerability triggers when the modem processes incoming reconfiguration messages from the network. No special configuration is required for the flaw to exist - it is present in the firmware itself.Affected if The device has an active cellular modem connection (the vulnerability is triggered passively by processing network messages)
If your device uses any of the listed Qualcomm chipsets (Apq8009, Apq8017, Apq8037, Aqt1000, Ar8035, Fsm10055, Msm8108, Msm8208) as its cellular modem, you are affected by this vulnerability regardless of configuration, as the flaw exists in all firmware versions of these products.
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 updates for affected Snapdragon chipsets. Contact device manufacturers (phones, IoT devices, vehicle systems) for modem firmware patches addressing this vulnerability.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.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 $7,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25702 — 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-25702 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