CVE-2023-33112
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 when WLAN firmware receives "reassoc response" frame including RIC_DATA element.
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 WLAN firmware where processing a reassoc response frame containing a RIC_DATA element causes a transient failure, likely due to improper handling of the RIC (Radio Resource Measurement Information Container) data in the firmware's reassociation state machine.
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 wireless chipset modelCheck the device's wireless chipset documentation, lspci output for PCIe WiFi cards, or lsusb for USB adapters. Look for model numbers matching Ar8035, Csra6620, Csra6640, Fastconnect 6200/6700/6900/7800, or Flight RB5 5G.Affected if The device uses any of the listed Qualcomm chipset models (Ar8035, Csra6620, Csra6640, Fastconnect 6200/6700/6900/7800, or Flight RB5 5G).
-
Confirm firmware versionUse vendor-specific commands such as 'iw list', 'wpa_cli status', or the chipset's diagnostic tool to retrieve the installed firmware version string. Compare against the affected product list.Affected if Firmware version matches any of the listed Qualcomm products (all versions of Ar8035, Csra6620, Csra6640, Fastconnect 6200/6700/6900/7800, Flight RB5 5G are affected).
-
Check for reassociation activityMonitor wireless traffic using tcpdump or Wireshark with a monitor mode interface. Filter for reassociation request/response frames (frame type 2, subtype 0xA or 0xB). Look for RIC_DATA elements (IE type 66) within these frames.Affected if The wireless interface processes reassociation frames containing RIC_DATA elements (IE type 66).
-
Review system logs for anomaliesCheck kernel logs (dmesg), wpa_supplicant logs, or vendor-specific daemon logs for error messages related to reassociation failures, firmware crashes, or radio resets occurring after reassociation events.Affected if Logs show repeated reassociation failures, firmware assertions, or wireless interface resets correlated with reassociation frame processing.
-
Verify monitor mode capabilityEnable monitor mode with 'iw dev <interface> monitor' or similar tool. Capture and analyze reassoc frames for malformed or unexpected RIC_DATA element structures using a packet analyzer.Affected if Reassociation frames with RIC_DATA elements are observed being processed by the affected device.
A device is affected if it uses any of the listed Qualcomm wireless chipsets (Ar8035, Csra6620, Csra6640, Fastconnect 6200/6700/6900/7800, or Flight RB5 5G) and processes reassociation frames containing RIC_DATA elements, potentially exhibiting reassociation failures or wireless interface resets.
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/driver updates for affected wireless hardware. Until patches are available, network monitoring may help detect anomalous reassoc frames.
- Consultation8.0 h
- Implementation4.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 $6,784.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33112 — 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-2023-33112 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