dbcve.org
Aqt1000 FirmwareOperating system · Qualcomm

CVE-2023-28544

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 while sending transmit command from HLOS to UTF handlers.

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 subsystem that occurs when sending transmit commands from the HLOS (High Level Operating System) to UTF handlers. The flaw allows potential code execution or denial of service due to improper memory handling during the inter-component communication between the OS and wireless firmware.

MitigationApply vendor-specific firmware/driver patches for affected WLAN components; implement proper memory validation and bounds checking in the transmit command path from HLOS to UTF handlers.

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
Ar9380 FirmwareOperating system
Affected:all versions
Csr8811 FirmwareOperating system
Affected:all versions
Csra6620 FirmwareOperating system
Affected:all versions
Csra6640 FirmwareOperating system
Affected:all versions
Fastconnect 6200 FirmwareOperating system
Affected:all versions
Fastconnect 6700 FirmwareOperating system
Affected:all versions
Fastconnect 6800 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 Qualcomm WLAN hardware
    Run system commands to list wireless network adapters (e.g., 'lspci -v', 'lsusb -v', or 'ip link show' on Linux; 'Get-NetAdapter' in PowerShell on Windows). Look for model numbers matching the affected list: Aqt1000, Ar9380, Csr8811, Csra6620, Csra6640, Fastconnect 6200, Fastconnect 6700, Fastconnect 6800.
    Affected if Any of the listed Qualcomm WLAN hardware models are present in the system
  2. Retrieve WLAN firmware version
    Query the wireless adapter firmware version using platform-specific tools (e.g., 'ethtool -i wlan0' on Linux, 'driverquery' on Windows, or firmware diagnostic utilities provided by the device OEM). Compare the firmware version against the affected product list noting that all versions are affected.
    Affected if The retrieved firmware version corresponds to any of the affected Qualcomm products (all versions are vulnerable)
  3. Verify WLAN driver is loaded
    Check if the wireless driver is active and the WLAN interface is up (e.g., 'ip link show', 'iwconfig', or 'Get-NetAdapter' in PowerShell). The vulnerability triggers when transmit commands flow from HLOS to UTF handlers.
    Affected if The WLAN interface is active and the driver is loaded, enabling the HLOS-to-UTF transmit command path
  4. Confirm UTF handler path is in use
    Inspect system or driver logs for any transmit-related activity involving UTF (Universal Test Fixture) handlers. On Linux, check 'dmesg' or '/var/log/syslog' for WLAN transmit command events. This is the specific communication channel where the memory corruption occurs.
    Affected if Transmit commands from HLOS to UTF handlers are being processed by the WLAN subsystem

If the system contains any of the affected Qualcomm WLAN firmware components (Aqt1000, Ar9380, Csr8811, Csra6620, Csra6640, Fastconnect 6200, 6700, or 6800) and the WLAN interface is active, the environment is affected by this vulnerability.

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-specific firmware/driver patches for affected WLAN components; implement proper memory validation and bounds checking in the transmit command path from HLOS to UTF handlers.

Fix this in Aqt1000 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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