CVE-2022-25685
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 module due to improper authorization while error handling in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, 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 confidenceDenial of service vulnerability in the modem module of Qualcomm Snapdragon chipsets (Auto, Compute, Consumer IOT, Industrial IOT, Mobile, Wearables) stems from improper authorization handling during error conditions. This flaw can potentially allow an attacker to trigger a modem crash or make it unresponsive by exploiting the flawed error handling path that lacks proper authorization checks.
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 Qualcomm chipset in the environmentInventory all hardware components to determine if any of the following Qualcomm products are present: Apq8009, Apq8017, Apq8037, Aqt1000, Ar8035, Csra6620, Csra6640, Msm8108. Check device datasheets, hardware SBOM, or firmware images.Affected if Any of the listed Qualcomm products/chipsets are present in the environment
-
Check modem firmware versionAccess the device firmware or use manufacturer diagnostic tools to retrieve the modem firmware version. For embedded devices, this may require UART/JTAG access or firmware extraction.Affected if The firmware version cannot be determined or matches one of the affected product names (all versions of these products are affected)
-
Verify modem interface exposureCheck network configuration, firewall rules, and device access controls to determine if the modem interface (AT commands port, QMI interface, or radio interface) is accessible from network segments or untrusted interfaces.Affected if The modem interface is exposed to untrusted network segments or provides unauthenticated access
If your environment contains any of the listed Qualcomm chipset products (Apq8009, Apq8017, Apq8037, Aqt1000, Ar8035, Csra6620, Csra6640, Msm8108) with an accessible modem interface, you are potentially affected by this vulnerability.
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 the Qualcomm firmware/security patch through OEM/OEM channels; until then, monitor network traffic for anomalous patterns targeting the modem interface and restrict physical and network access to reduce attack surface.
- Consultation6.0 h
- Implementation24.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 $14,016.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25685 — 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-25685 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