CVE-2022-25673
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 configuration from network 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 denial of service vulnerability exists in the Qualcomm Snapdragon Mobile modem component where an assertion can be triggered when processing malformed network configuration data. An attacker sending specially crafted configuration messages from the network can cause the modem to crash or become unavailable, affecting voice and data services.
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 modem firmware versionAccess the device's modem diagnostic interface or use AT commands (such as ATI or AT+GMR) to query the firmware version. On Android devices, this information may also be available under Settings > About Phone > SIM Status or through engineering mode menus.Affected if The reported firmware version matches any of the following: Ar8035, Qca8081, Qca8337, Qcn6024, Qcn9024, Sd 8 Gen1 5g, Sdx65, or Wcd9380.
-
Confirm the chipset vendorCheck the device specifications or modem documentation to verify the chipset manufacturer is Qualcomm. This may be listed in the device's technical specifications, baseband information, or obtained via AT command responses.Affected if The modem uses a Qualcomm Snapdragon or Qualcomm-branded chipset.
-
Check for network configuration handlingVerify the device is capable of receiving network configuration data from carrier networks. This is standard for any cellular device that connects to voice or data networks.Affected if The device has active cellular connectivity or SIM card functionality, as processing network configuration messages is required for normal operation.
If the device uses any of the listed Qualcomm firmware components (Ar8035, Qca8081, Qca8337, Qcn6024, Qcn9024, Sd 8 Gen1 5g, Sdx65, or Wcd9380) and processes network configuration data, it is 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 firmware updates provided by device manufacturers as they become available from Qualcomm. Until patches are deployed, monitor network traffic for anomalies targeting modem configuration interfaces.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25673 — 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-25673 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