dbcve.org
Aqt1000 FirmwareOperating system · Qualcomm

CVE-2022-25736

HIGH · 7.5 CVSS v3.1 Published 2022-10-19
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
Denial of service in WLAN due to out-of-bound read happens while processing VHT action frame in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking

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

Out-of-bounds read vulnerability in the WLAN component of Qualcomm Snapdragon chipsets when processing VHT (Very High Throughput) action frames. A remote attacker can send a specially crafted VHT action frame to trigger memory reads beyond allocated buffer boundaries, causing a denial of service condition.

MitigationApply vendor-provided firmware/security patches from Qualcomm and downstream device manufacturers. Until patches are available, network-level filtering of malformed VHT action frames may provide partial mitigation.

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
Ar8035 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

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 Qualcomm WLAN chipset model
    Access the device's system information or network adapter details to list the wireless chipset. Common methods: 'lspci -v' for PCIe cards, 'iw list' for Linux wireless devices, or check device hardware specifications. Look for chip identifiers such as Aqt1000, Ar8031, Ar8035, Ar9380, Csr8811, Csra6620, Csra6640, or Csrb31024.
    Affected if The device uses any of the following chipsets: Aqt1000, Ar8031, Ar8035, Ar9380, Csr8811, Csra6620, Csra6640, or Csrb31024.
  2. Verify WLAN firmware version
    Query the wireless firmware version through vendor-specific tools (e.g., 'ath10kutil', 'qca-nss-drv', or device management interfaces). Check firmware files in /lib/firmware or equivalent path on embedded devices. Consult chipset documentation for version query commands.
    Affected if The chipset firmware version matches any of the affected models (all versions of the listed chipsets are vulnerable).
  3. Confirm WLAN functionality is active
    Check if the wireless interface is up and running. On Linux: 'ip link show' or 'iw dev'. On embedded devices: check WLAN status via vendor management UI or debug logs. The vulnerability requires active WLAN processing.
    Affected if WLAN interface is enabled and actively processing wireless frames.
  4. Check if VHT (Very High Throughput) is enabled
    Inspect wireless interface capabilities and current configuration. On Linux: 'iw list' shows supported VHT capabilities, 'iw dev <interface> info' shows current VHT status. VHT operates on 5GHz band. The flaw triggers when processing VHT action frames.
    Affected if VHT support is enabled on the wireless interface, making it susceptible to malformed VHT action frame injection.

A user is affected if their device contains any of the listed Qualcomm chipsets (Aqt1000, Ar8031, Ar8035, Ar9380, Csr8811, Csra6620, Csra6640, Csrb31024) and has WLAN with VHT functionality enabled, since all firmware versions of these chipsets 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 firmware/security patches from Qualcomm and downstream device manufacturers. Until patches are available, network-level filtering of malformed VHT action frames may provide partial mitigation.

Fix this in Aqt1000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
40.0 hours of engineering $6,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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