CVE-2022-33254
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 while processing SIB1 Message.
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 can be triggered during processing of SIB1 (System Information Block 1) messages, causing a transient denial of service condition. This vulnerability exists in the cellular modem component and can be exploited by a remote attacker sending specially crafted SIB1 messages.
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 hardwareInspect system hardware inventory, device tree, or PCIe/USB device listings for presence of Aqt1000, Ar8035, Qca6390, Qca6391, Qca6421, Qca6426, Qca6431, or Qca6436 modem chips. On Linux, 'lspci' or 'lsusb' may reveal these devices. Check bootloader or hardware schematics if you have access.Affected if Any of the listed Qualcomm modem part numbers (Aqt1000, Ar8035, Qca6390/Qca6391/Qca6421/Qca6426/Qca6431/Qca6436) are present in the system
-
Check cellular modem firmware versionQuery the modem firmware version through vendor-specific AT commands (e.g., 'AT+CGMR' or 'AT+GMR'), or via the host interface API provided by the modem driver. Compare the reported version against the affected product list.Affected if The firmware version corresponds to any of the listed products (all versions are affected)
-
Verify cellular modem is activeCheck if the cellular modem interface is up and registered on a network. On Linux, 'ip link show' or 'iw dev' may list cellular interfaces. Verify network registration status via 'AT+CEREG?' or similar operator status commands.Affected if The cellular modem is powered on and connected to a cellular network, making it capable of receiving SIB1 messages
-
Examine modem logs for assertion failuresReview modem debug logs, kernel logs (dmesg), or vendor-specific logs for messages containing 'assertion failed', 'assert', or modem crash/reboot events. These may indicate the vulnerability was triggered.Affected if Assertion failures or modem restarts coincide with SIB1 message processing timestamps or network registration events
If your system contains any of the listed Qualcomm modem chips (Aqt1000, Ar8035, Qca6390/Qca6391/Qca6421/Qca6426/Qca6431/Qca6436) and the cellular modem is active, you are likely 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-provided firmware updates for affected modem components. In cellular infrastructure contexts, ensure proper message validation is enabled and monitor for assertion failures in modem logs.
- Consultation8.0 h
- Implementation4.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,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33254 — 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-33254 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