CVE-2022-25689
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 in Snapdragon Mobile
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 reachable assertion in the Modem component of Snapdragon Mobile processors allows an attacker to trigger a denial of service condition. The vulnerability stems from insufficient input validation that enables an attacker-controlled scenario to hit an assertion intended for debugging, causing the modem to crash or become unresponsive.
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 modem chip modelExamine device hardware specifications, FCC ID, or system information to determine if the device contains one of the affected modem chips: Ar8035, Qca8081, Qca8337, Qcn6024, Qcn9024, Sdx65, Wcd9380, or Wcn6855. On Linux systems, check via 'lspci' for network controllers or 'cat /proc/device-tree/model' for embedded devices.Affected if The device uses any of the listed Qualcomm modem chips (all versions are affected).
-
Check the installed modem firmware versionQuery the modem firmware version through vendor-specific interfaces. On Android devices, check via 'at+ver' or 'at+cgmr' AT commands, or through '/sys/class/net/*/device/firmware_version'. For routers/enterprise equipment, use SNMP, web UI, or CLI commands like 'show version' or 'cat /proc/ath9k/fw' for Atheros/Qualcomm chips.Affected if Any firmware version is present on the affected chip models, as all versions are vulnerable.
-
Determine if the modem is exposed to untrusted network inputsReview network architecture and firewall rules to assess whether the modem component can receive crafted input from untrusted sources. Check if there are ACLs, packet filters, or network segmentation between the WAN/internet and the modem processor.Affected if The modem directly accepts input from untrusted network sources without filtering, enabling the attack vector.
The environment is affected if any device uses the listed Qualcomm modem firmware components (Ar8035, Qca8081, Qca8337, Qcn6024, Qcn9024, Sdx65, Wcd9380, Wcn6855), as all firmware versions contain the 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 vendor-supplied firmware patches from Qualcomm and coordinate with device manufacturers for OTA updates. Network operators may implement traffic filtering as an interim measure to block malformed inputs reaching the modem.
- Consultation8.0 h
- Implementation40.0 h
- Testing24.0 h
- Review / QA16.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $24,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25689 — 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-25689 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