dbcve.org
Csr8811 FirmwareOperating system · Qualcomm

CVE-2023-33016

HIGH · 7.5 CVSS v3.1 Published 2023-09-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Transient DOS in WLAN firmware while parsing MLO (multi-link operation).

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 confidence

A denial-of-service vulnerability exists in WLAN firmware during the parsing of Multi-Link Operation (MLO) frames. The vulnerability can be exploited remotely (network-accessible) to cause a transient crash or hang in the wireless subsystem, potentially requiring a reboot or reconnection to recover.

MitigationApply vendor-supplied firmware updates that address this vulnerability. If no patch is available, consider network segmentation to limit exposure of affected WLAN devices or disable MLO features where feasible.

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 data
Csr8811 FirmwareOperating system
Affected:all versions
Fastconnect 6900 FirmwareOperating system
Affected:all versions
Fastconnect 7800 FirmwareOperating system
Affected:all versions
Immersive Home 214 FirmwareOperating system
Affected:all versions
Immersive Home 216 FirmwareOperating system
Affected:all versions
Immersive Home 316 FirmwareOperating system
Affected:all versions
Immersive Home 318 FirmwareOperating system
Affected:all versions
Ipq5010 FirmwareOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the WiFi hardware in the system
    On Linux, run `lspci -nnk | grep -i network` or `lsusb` for USB WiFi adapters. On Windows, open Device Manager and expand Network adapters. Look for Qualcomm wireless adapters such as Csr8811, Fastconnect 6900/7800, Immersive Home series, or Ipq5010.
    Affected if The system contains any of the following Qualcomm chips: Csr8811, Fastconnect 6900, Fastconnect 7800, Immersive Home 214, 216, 316, 318, or Ipq5010.
  2. Verify the wireless driver and firmware version
    On Linux, use `iw list` or check `/proc/version`. For firmware details, check `dmesg | grep -i wifi` or `dmesg | grep -i firmware`. On Windows, right-click the WiFi adapter in Device Manager, select Properties, and view the Driver and Firmware version tabs.
    Affected if The driver or firmware version matches any of the affected Qualcomm products listed, regardless of version number.
  3. Check if Multi-Link Operation (MLO) feature is enabled
    On Linux, run `iw list` and look for 'MLO' or 'Multi-Link' in the supported capabilities. Check active interface configuration with `iw dev <interface> info`. If the system uses hostapd or wpa_supplicant, examine their configuration files (typically in /etc/hostapd/ or /etc/wpa_supplicant/) for MLO-related settings.
    Affected if MLO (Multi-Link Operation) is enabled in the wireless configuration or supported by the driver, making the device capable of processing MLO frames.
  4. Verify the wireless subsystem is actively using WiFi
    Run `ip link show` or `iw dev` to confirm an active wireless interface exists and is up. Check if the system has active WiFi connections with `nmcli device status` (NetworkManager) or `iw <interface> link`.
    Affected if The system has an active WiFi interface using the affected Qualcomm hardware, and that interface supports or has MLO enabled.

A system is affected if it contains any of the listed Qualcomm WiFi chips (Csr8811, Fastconnect 6900/7800, Immersive Home 214/216/316/318, Ipq5010) and has MLO functionality enabled or supported, regardless of firmware version since all versions are vulnerable.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware updates that address this vulnerability. If no patch is available, consider network segmentation to limit exposure of affected WLAN devices or disable MLO features where feasible.

Fix this in Csr8811 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-33016 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-33016 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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