dbcve.org
315 5g Iot FirmwareOperating system · Qualcomm

CVE-2023-28573

HIGH · 7.8 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 →
80/100
Remediation priority · High
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
Memory corruption in WLAN HAL while parsing WMI command parameters.

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

Memory corruption vulnerability in the WLAN Hardware Abstraction Layer (HAL) occurring during parsing of WMI (Wireless Management Interface) command parameters. The vulnerability allows local attackers to corrupt memory, potentially leading to denial of service or privilege escalation.

MitigationApply vendor-provided security patches for the WLAN HAL/driver component. Given the high CVSS score and memory corruption nature, prioritize rapid deployment to mitigate risk of local privilege escalation or system instability.

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
315 5g Iot FirmwareOperating system
Affected:all versions
Aqt1000 FirmwareOperating system
Affected:all versions
Ar8035 FirmwareOperating system
Affected:all versions
Ar9380 FirmwareOperating system
Affected:all versions
Csr8811 FirmwareOperating system
Affected:all versions
Csrb31024 FirmwareOperating system
Affected:all versions
Fastconnect 6200 FirmwareOperating system
Affected:all versions
Fastconnect 6700 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 installed wireless hardware
    Check system for Qualcomm wireless adapters using 'lspci' for PCIe, 'lsusb' for USB, or check device tree/system info for embedded modules. Look for product names: 315 5G IoT, Aqt1000, Ar8035, Ar9380, Csr8811, Csrb31024, Fastconnect 6200, Fastconnect 6700.
    Affected if The system contains any of the listed Qualcomm wireless chips (315 5G IoT, Aqt1000, Ar8035, Ar9380, Csr8811, Csrb31024, Fastconnect 6200, or Fastconnect 6700).
  2. Check WLAN firmware version
    Query the wireless firmware version through the device driver or firmware management interface. On Linux, this may be accessible via 'iw', 'wpa_supplicant' logs, or by reading firmware version from '/sys/class/net/*/device/firmware_version' or similar paths depending on the device.
    Affected if The installed firmware version is any version (all versions of these products are affected per the CVE).
  3. Verify WLAN interface is active
    Check if any wireless interface is up using 'ip link show' or 'ifconfig -a'. Look for interfaces with wireless extensions (wlan*, wl*, ath*, etc.).
    Affected if A wireless interface associated with the affected Qualcomm hardware is present and enabled (the vulnerability triggers during WMI command parsing when WLAN is active).
  4. Check WLAN HAL driver module
    Identify the kernel module or driver handling the WLAN HAL. On Linux, use 'lsmod' to list loaded modules and check for Qualcomm WLAN drivers (may include qca, ath, cnss, or vendor-specific modules). Query module info via 'modinfo <module_name>' if identified.
    Affected if A Qualcomm WLAN HAL driver module is loaded and the device is in use. The vulnerability exists in the HAL's WMI parameter parsing code path.

If the system uses any of the listed Qualcomm wireless chips (315 5G IoT, Aqt1000, Ar8035, Ar9380, Csr8811, Csrb31024, Fastconnect 6200, Fastconnect 6700) with WLAN enabled, the environment is affected since all firmware versions of these products 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-provided security patches for the WLAN HAL/driver component. Given the high CVSS score and memory corruption nature, prioritize rapid deployment to mitigate risk of local privilege escalation or system instability.

Fix this in 315 5g Iot Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Check whether your project pulls in CVE-2023-28573 — 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-28573 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