dbcve.org
Aqt1000 FirmwareOperating system · Qualcomm

CVE-2023-28564

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 passing command parameters through WMI interfaces.

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) when processing command parameters passed through WMI (Wireless Management Interface) interfaces. This could allow an attacker to corrupt memory and potentially achieve arbitrary code execution with elevated privileges.

MitigationApply firmware updates from the affected device/vendor that address the WLAN HAL memory corruption. If no update is available, consider network segmentation to limit exposure of affected wireless components.

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
Aqt1000 FirmwareOperating system
Affected:all versions
Ar8031 FirmwareOperating system
Affected:all versions
Ar9380 FirmwareOperating system
Affected:all versions
Csr8811 FirmwareOperating system
Affected:all versions
Csra6620 FirmwareOperating system
Affected:all versions
Csra6640 FirmwareOperating system
Affected:all versions
Csrb31024 FirmwareOperating system
Affected:all versions
Fastconnect 6200 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 Qualcomm wireless hardware in the system
    Run 'lspci -v' or 'lsusb -v' or check device manager to list wireless network adapters. Look for devices with Qualcomm Aqt1000, Ar8031, Ar9380, Csr8811, Csra6620, Csra6640, Csrb31024, or Fastconnect 6200 chipset identifiers.
    Affected if Any of the listed Qualcomm wireless chipsets (Aqt1000, Ar8031, Ar9380, Csr8811, Csra6620, Csra6640, Csrb31024, Fastconnect 6200) are present in the system
  2. Check firmware version of Qualcomm wireless device
    Use vendor-specific tools (such as 'athdiag', 'iwevent', or manufacturer diagnostic utilities) or check /sys/class/net/*/device/firmware_version (on Linux) to read the installed firmware version of the Qualcomm wireless adapter.
    Affected if The firmware version matches one of the affected products and cannot be determined or is confirmed to be any version (all versions affected)
  3. Verify WMI/Wireless Management Interface is active
    Check if the wireless interface is enabled and running using 'iwconfig', 'ip link show', or 'netsh wlan show interfaces' on Windows. The vulnerability triggers through WMI command parameter processing.
    Affected if The wireless interface is active and the WMI service handling wireless commands is enabled (vulnerability requires WMI interface to process malicious commands)
  4. Check for wireless driver version and vendor support status
    Review the wireless driver logs, driver version via 'ethtool -i <interface>' on Linux or driver details in Device Manager on Windows, then check the device vendor website for available firmware updates.
    Affected if The driver/firmware combination is from an affected product line and no vendor patch has been applied

A system is affected if it contains any of the listed Qualcomm wireless chipsets (Aqt1000, Ar8031, Ar9380, Csr8811, Csra6620, Csra6640, Csrb31024, Fastconnect 6200) with all versions being vulnerable, and the wireless interface with WMI is active.

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 firmware updates from the affected device/vendor that address the WLAN HAL memory corruption. If no update is available, consider network segmentation to limit exposure of affected wireless components.

Fix this in Aqt1000 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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