CVE-2022-25734
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 missing null check while processing IP packets with padding
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 modem firmware where a missing null check during IP packet processing with padding allows an attacker to crash the modem by sending specially crafted IP packets.
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 modem hardware modelLocate the modem hardware in your device or system documentation, or run commands such as 'at+cgmm' (for AT-command accessible modems), 'lspci' for PCIe modems, or check kernel logs for Qualcomm modem detectionAffected if The modem model matches any of: Ar8031, Csra6620, Csra6640, Mdm8207, Mdm9205, Mdm9206, Mdm9207, or Mdm9607
-
Determine modem firmware versionQuery the modem firmware version via AT commands (such as 'at+cgmr' or vendor-specific commands), check system firmware logs, or use vendor diagnostic tools if availableAffected if Any firmware version is returned - all versions of the listed modems are affected by this CVE
-
Verify IP packet processing is enabledCheck if the modem is configured for IP packet handling. This may be indicated by PDP context activation, data connection status, or network interface presence (check with 'ip link' or 'ifconfig' for modem interfaces such as rmnet, qmi, orwwan)Affected if The modem has an active data connection or IP network interface configured, as the vulnerability triggers during IP packet processing with padding
-
Assess network exposureDetermine if the modem is directly accessible from untrusted networks. Check firewall rules, ACLs, or network segmentation around the modem data interfaceAffected if The modem data interface is accessible from network segments beyond trusted internal networks, creating an attack vector for crafted IP packets
Your environment is affected if any device uses the listed Qualcomm modem firmware variants (Ar8031, Csra6620, Csra6640, Mdm8207, Mdm9205, Mdm9206, Mdm9207, Mdm9607) with IP packet processing enabled and network accessibility.
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-provided firmware updates that include proper null validation in IP packet handling code; if no update is available, contact the modem vendor for remediation guidance.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25734 — 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-25734 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