dbcve.org
Apq8096au FirmwareOperating system · Qualcomm

CVE-2022-25690

HIGH · 7.5 CVSS v3.1 Published 2022-09-16
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
Information disclosure in WLAN due to improper validation of array index while parsing crafted ANQP action frames in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music

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

This is an information disclosure vulnerability in Qualcomm Snapdragon WLAN firmware where improper validation of array index during parsing of crafted ANQP (Access Network Query Protocol) action frames allows an attacker to read sensitive memory contents. The flaw enables an adjacent network attacker to send malicious ANQP frames that trigger out-of-bounds reads due to missing bounds checking on array indices.

MitigationApply vendor-supplied firmware updates for affected Snapdragon chipsets; until updates are available, disable 802.11u/ANQP functionality or restrict network access to trusted WLAN environments.

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
Apq8096au FirmwareOperating system
Affected:all versions
Aqt1000 FirmwareOperating system
Affected:all versions
Ar8031 FirmwareOperating system
Affected:all versions
Ar8035 FirmwareOperating system
Affected:all versions
Csra6620 FirmwareOperating system
Affected:all versions
Csra6640 FirmwareOperating system
Affected:all versions
Csrb31024 FirmwareOperating system
Affected:all versions
Mdm9250 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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 WLAN chipset model
    Run 'lspci -k' for PCIe cards, 'lsusb' for USB adapters, or check 'dmesg | grep -i wlan' for kernel messages showing the wireless chipset. Match the chipset name against the affected list: Apq8096au, Aqt1000, Ar8031, Ar8035, Csra6620, Csra6640, Csrb31024, or Mdm9250.
    Affected if The device uses any of the listed Qualcomm chipsets (all versions are affected)
  2. Confirm firmware version
    Check the WLAN firmware version via 'iw dev <interface> info' or by reading firmware binary details from /lib/firmware/qca/ or similar firmware directories. Note that all firmware versions of affected chipsets are vulnerable.
    Affected if The chipset is on the affected list regardless of version (all versions are affected)
  3. Verify if 802.11u is enabled
    Check wireless interface capabilities and configuration using 'iw dev <interface> info' or 'iw list' to see if the device advertises 802.11u (Hotspot 2.0) support. For AP/AC routers, also inspect hostapd configuration files for 'hs20' or 'interworking' settings.
    Affected if 802.11u/Hotspot 2.0 functionality is enabled on the interface
  4. Check if ANQP processing is active
    Use 'iw mon0 survey dump' or capture wireless traffic with 'tcpdump -i <interface> -w capture.pcap' to look for ANQP action frames (frame subtype 0x11d). Also check if the device responds to ANQP queries from other devices.
    Affected if The device processes or responds to ANQP action frames from adjacent devices

A user is affected if their device contains one of the listed Qualcomm WLAN chipsets and has 802.11u/ANQP functionality enabled, allowing nearby attackers to send crafted ANQP frames that trigger out-of-bounds memory reads.

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 for affected Snapdragon chipsets; until updates are available, disable 802.11u/ANQP functionality or restrict network access to trusted WLAN environments.

Fix this in Apq8096au Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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