CVE-2022-33270
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 time-of-check time-of-use race condition in Modem while processing RRC Reconfiguration 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 time-of-check time-of-use (TOCTOU) race condition in the Modem component allows an attacker to cause a transient denial of service by sending a specially crafted RRC (Radio Resource Control) Reconfiguration message. The vulnerability exploits a timing window between when the modem checks a condition and when it uses that condition result during message processing.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 Qualcomm modem chipset modelCheck your device documentation, system information, or modem firmware settings to determine if the chipset is one of: Ar8035, Wcn3998, Wcn6750, Wcn685x (5 or 1), Wcn785x (1 or 5), or Qca6391Affected if The device uses any of these Qualcomm modem chipsets
-
Locate the modem firmware versionAccess the modem or baseband firmware information through device settings, diagnostic tools, or AT command interface (for mobile devices) to retrieve the installed firmware versionAffected if The firmware version cannot be determined or matches the affected chipset list
-
Determine if RRC Reconfiguration message processing is activeMonitor or inspect modem message processing to confirm the device handles RRC (Radio Resource Control) messages, which is standard for cellular communicationAffected if The modem processes RRC messages (typical for any cellular-connected device)
-
Check vendor security advisoriesReview the device or Qualcomm vendor security advisories to confirm if a patch for CVE-2022-33270 has been released for your specific firmware versionAffected if No patch has been released or applied for this CVE
You are affected if your device uses any of the listed Qualcomm modem chipsets (Ar8035, Wcn3998, Wcn6750, Wcn685x 5/1, Wcn785x 5/1, Qca6391) and processes RRC messages without having applied a vendor firmware patch for 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/security patches for the affected modem component. Until a patch is available, consider network-level filtering or monitoring for anomalous RRC Reconfiguration messages.
- Consultation4.0 h
- Implementation12.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33270 — 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-33270 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