CVE-2023-33026
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 in WLAN Firmware while parsing a NAN management frame.
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 high-severity denial of service vulnerability exists in WLAN firmware when parsing NAN (Neighbor Awareness Networking) management frames. The firmware fails to properly handle or validate malformed NAN frames, causing a transient crash or hang that disrupts wireless connectivity.
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 wireless chipset in useCheck the system's wireless adapter chipset (e.g., via lspci, lsusb, or device manufacturer documentation). Look for Qualcomm brand identifiers such as Ar8035, Ar9380, Csr8811, Wcn6750, Wcn685x, or Wcn785x.Affected if The chipset matches one of the listed affected Qualcomm part numbers (Ar8035, Ar9380, Csr8811, Wcn6750, Wcn685x, Wcn785x).
-
Check if NAN (Neighbor Awareness Networking) is enabledInspect the wireless interface configuration for NAN settings. On Linux, use 'iw list' to check for NAN interface support or look for 'nan' in the interface type list. On Windows, check wireless adapter properties for NAN/Neighbor Awareness Networking.Affected if NAN functionality is enabled or available on the wireless adapter.
-
Determine the WLAN firmware versionQuery the wireless firmware version through the operating system or device firmware interface. On Linux, check /sys/class/net/*/device/firmware_version or use 'ethtool -i' on the wireless interface. On embedded devices, consult manufacturer documentation or the device's firmware information page.Affected if The installed firmware version is an unpatched release (all versions of the listed products are affected before vendor patch application).
-
Monitor for wireless connectivity disruptionsReview system logs (e.g., dmesg, /var/log/syslog, Windows Event Viewer) for wireless driver or firmware crash messages, particularly those mentioning NAN, wireless hang, or firmware fault occurring after wireless activity.Affected if The system experiences unexplained wireless drops, hangs, or firmware crashes, especially during periods of active wireless scanning or NAN discovery.
The system is affected if it uses any of the listed Qualcomm wireless chipsets (Ar8035, Ar9380, Csr8811, Wcn6750, Wcn685x, or Wcn785x) with NAN functionality enabled and is running an unpatched firmware version.
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 the vendor-provided firmware patch for the WLAN component. If no patch is available, consider disabling NAN functionality or implementing network-level filtering to block potentially malicious NAN frames.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33026 — 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-33026 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