CVE-2022-25675
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 due to reachable assertion in modem while processing filter rule from application client in Snapdragon Compute, Snapdragon Industrial IOT, 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 can be triggered when processing malformed filter rules from an application client. This causes the modem to crash, resulting in denial of service. The vulnerability affects Qualcomm Snapdragon modem firmware in Compute, Industrial IOT, and Mobile product lines.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 chipset modelCheck device settings or system information for baseband/modem chipset details. On Android, this may appear under Settings > About Phone > Baseband, or via *#*#4636#*#* menu, or terminal commands like 'getprop ro.baseband' or 'getprop gsm.version.baseband'. On other platforms, consult OEM documentation for accessing modem firmware information.Affected if The chipset model matches any of: Aqt1000, Qca6310, Qca6320, Qca6390, Qca6391, Qca6420, Qca6430, or Qcm6490
-
Confirm the firmware versionRetrieve the installed modem firmware version using available diagnostic tools, OEM-specific AT commands (such as AT+CGMR or ATI), or through the device's engineering mode. Record the exact version string returned.Affected if The modem firmware version is present and corresponds to any of the affected chipset models listed (all versions of these chipsets are affected per the advisory).
-
Verify the device uses Snapdragon modemConfirm the device utilizes a Qualcomm Snapdragon modem platform. This may be identifiable through the processor/modem documentation, specification sheets, or by checking if the baseband firmware identifier contains Qualcomm or Snapdragon references.Affected if The device incorporates a Qualcomm Snapdragon modem in the affected product lines (Compute, Industrial IOT, or Mobile).
If the device contains any of the listed modem chipsets (Aqt1000, Qca6310, Qca6320, Qca6390, Qca6391, Qca6420, Qca6430, or Qcm6490) with any firmware version, the environment 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 vendor-supplied firmware updates from Qualcomm/OEM to patch the modem baseband processor. Users should update device firmware through carrier or manufacturer channels.
- Consultation4.0 h
- Implementation8.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,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25675 — 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-25675 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