CVE-2022-33244
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 reachable assertion in modem during MIB reception and SIB timeout
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 firmware triggers a transient denial of service during MIB (Master Information Block) reception when a SIB (System Information Block) timeout occurs. The vulnerability allows an attacker to cause the modem to crash or become unavailable by sending specifically crafted signals that trigger the assertion failure.
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 installed modem hardware modelCheck system inventory, hardware documentation, or use commands like 'lspci', 'lsusb', or vendor-specific tools to list network/modem hardware. Look for Qualcomm model identifiers such as Ar8035, Qca6391, Qca8081, Qca8337, Qcm6490, Qcn6024, Qcn9024, or Qcs6490.Affected if The system contains any of the listed Qualcomm modem models (Ar8035, Qca6391, Qca8081, Qca8337, Qcm6490, Qcn6024, Qcn9024, Qcs6490).
-
Determine the current modem firmware versionUse vendor-provided tools or AT commands (for cellular modems) to query the installed firmware version. Consult the device documentation for the specific command (for example, 'AT+GMR' for some modems or vendor-specific diagnostic interfaces).Affected if The firmware version is any version, as all versions of the listed products are affected by this CVE.
-
Review system logs for modem assertion failuresExamine system and kernel logs (such as /var/log/syslog, dmesg output, or vendor-specific log directories) for messages containing keywords like 'assertion', 'modem crash', 'modem reset', 'firmware error', or 'MIB' in proximity to network connectivity disruptions.Affected if Logs contain assertion failures or modem crash events occurring during MIB/SIB reception operations.
-
Monitor for unexpected modem connectivity disruptionsObserve network interface status and connectivity logs. Check for repeated or unexplained modem resets, complete loss of cellular/network connectivity, or service unavailability events that coincide with potential signaling activity.Affected if The modem exhibits repeated crashes, becomes unavailable, or shows frequent connection drops without other explanation.
A system is affected if it contains any of the listed Qualcomm modem firmware models (Ar8035, Qca6391, Qca8081, Qca8337, Qcm6490, Qcn6024, Qcn9024, or Qcs6490), since all versions of these products are vulnerable to the assertion-triggered denial of service during MIB reception.
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 for the modem component. Until a patch is available, monitor for modem connectivity disruptions and consider network-level protections against malformed signaling messages.
- 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-33244 — 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-33244 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