CVE-2022-33304
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 · uneditedTransient DOS due to NULL pointer dereference in Modem while performing pullup for received TCP/UDP packet.
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 NULL pointer dereference vulnerability in the Modem component occurs during the 'pullup' operation when processing received TCP/UDP packets, leading to a transient Denial of Service condition. The vulnerability stems from improper NULL pointer validation before dereferencing packet data structures.
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 modem hardware in the environmentInventory network devices, IoT devices, or embedded systems for components using Qualcomm 9205, 9206, 9207 LTE modems, Ar8031, Csra6620, Csra6640, or Wcn685x chipsets. Check device specifications, hardware BOMs, or system information for these chipset identifiers.Affected if The environment contains any device with the listed Qualcomm modem chipsets (9205, 9206, 9207, Ar8031, Csra6620, Csra6640, Wcn685x) regardless of firmware version.
-
Check modem firmware versionAccess the device management interface, bootloader, or firmware image and query the modem firmware version string. For embedded devices, this may require UART, JTAG, or manufacturer diagnostic tools. Look for version fields in AT command outputs (for modems) or firmware metadata.Affected if The modem firmware version matches any of the affected products: Qualcomm 9205, 9206, 9207 LTE Modem Firmware, Ar8031 Firmware, Csra6620 Firmware, Csra6640 Firmware, or Wcn685x Firmware (any version).
-
Verify modem network stack is activeConfirm the modem component is powered and initialized. Check system logs, process lists, or network interface status for active modem interfaces (often appears as rmnet, qmi, or cellular network interfaces). Monitor for TCP/UDP packet activity through the modem.Affected if The modem is powered on and its network stack is processing TCP/UDP packets, enabling the vulnerable 'pullup' code path.
-
Check for NULL pointer handling in packet processingAnalyze modem firmware or network traffic dumps for evidence of packet processing errors, crashes, or service interruptions related to TCP/UDP handling. Review system logs for modem restart events or denial of service indicators.Affected if The environment experiences transient modem crashes or network interruptions during active TCP/UDP packet processing, which may indicate exploitation of this NULL pointer dereference.
A user is affected if their environment contains any device with the listed Qualcomm modem chipsets (9205, 9206, 9207, Ar8031, Csra6620, Csra6640, Wcn685x) with active TCP/UDP packet processing, since all firmware versions of these components are vulnerable.
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 for the affected Modem component to address the NULL pointer handling in TCP/UDP packet processing.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33304 — 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-33304 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