dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2022-25748

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
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
Memory corruption in WLAN due to integer overflow to buffer overflow while parsing GTK frames. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon 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

Memory corruption vulnerability in Qualcomm Snapdragon WLAN driver where an integer overflow occurs during GTK (Group Temporal Key) frame parsing, leading to a buffer overflow that can corrupt memory. This occurs in the Wi-Fi firmware/software stack and could allow remote attackers to execute arbitrary code or cause denial of service.

MitigationApply vendor-supplied firmware updates for affected Snapdragon devices. This is a low-level WLAN firmware issue requiring patches from device/OEM manufacturers rather than application-level remediation.

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
Apq8009 FirmwareOperating system
Affected:all versions
Apq8017 FirmwareOperating system
Affected:all versions
Apq8076 FirmwareOperating system
Affected:all versions
Apq8096au FirmwareOperating system
Affected:all versions
Aqt1000 FirmwareOperating system
Affected:all versions
Ar8031 FirmwareOperating system
Affected:all versions
Ar8035 FirmwareOperating system
Affected:all versions
Ar9380 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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 the Qualcomm Wi-Fi chipset model
    Check system information via 'lspci | grep -i network' for PCIe Wi-Fi cards, 'lsusb' for USB adapters, or check device-specific files like '/sys/class/net/*/device/uevent' or '/proc/cpuinfo' on embedded devices. Look for the chipset identifier such as Apq8009, Apq8017, Apq8076, Apq8096au, Aqt1000, Ar8031, Ar8035, or Ar9380.
    Affected if The chipset matches any of the eight affected models: Apq8009, Apq8017, Apq8076, Apq8096au, Aqt1000, Ar8031, Ar8035, or Ar9380.
  2. Check the Wi-Fi firmware version
    Use vendor-specific commands to query the WLAN firmware version. On Linux, try 'cat /sys/class/net/*/device/firmware_version' or check '/etc/firmware' directory for Wi-Fi firmware files. On Android, use 'getprop' to query 'wlan.driver.version' or check through the Wi-Fi settings about page. The firmware version information format varies by device/OEM.
    Affected if The firmware version corresponds to any version of an affected chipset (all versions of the listed chipsets are vulnerable).
  3. Verify WLAN interface is present and active
    Check for wireless network interfaces using 'ip link show' or 'iwconfig'. Look for interfaces such as wlan0, wlp*, or similar. Verify the interface is up with 'ip link set <interface> up'.
    Affected if The device has an active Wi-Fi interface using the affected Qualcomm WLAN firmware, as the vulnerability triggers during GTK frame parsing in the Wi-Fi stack.
  4. Check the loaded WLAN driver module
    Run 'lsmod | grep -i wifi' or 'modinfo <driver_module>' to identify the WLAN driver. Check '/proc/kallsyms' or 'dmesg | grep -i wifi' for driver and firmware loading messages.
    Affected if The driver is the Qualcomm Snapdragon WLAN driver (often vendor-specific like 'qcacld' or similar) loaded with one of the affected firmware variants.
  5. Inspect system logs for WLAN firmware crashes or anomalies
    Review kernel logs with 'dmesg | grep -i wifi' or check '/var/log/syslog' for WLAN-related messages. Look for indicators of memory corruption, buffer overflow crashes, or unexpected firmware restarts in the Wi-Fi subsystem.
    Affected if The device exhibits Wi-Fi subsystem crashes, memory corruption symptoms, or unexpected reboots that correlate with WLAN activity, which may indicate exploitation of this vulnerability.
  6. Confirm device is a consumer/embedded product receiving firmware updates from the OEM
    Check the device documentation, support pages, or vendor security advisories to determine if the device manufacturer provides firmware update channels for the Wi-Fi chipset. Identify the original equipment manufacturer (OEM) and their support lifecycle status.
    Affected if The device uses an affected Qualcomm chipset but the OEM has not issued a firmware patch, leaving the vulnerability unaddressed in the currently running firmware.

The device is affected if it contains any of the eight listed Qualcomm chipsets (Apq8009, Apq8017, Apq8076, Apq8096au, Aqt1000, Ar8031, Ar8035, Ar9380) and is running the vendor-supplied Wi-Fi firmware, since all versions of these chipsets are vulnerable to the GTK frame parsing buffer overflow.

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 devices. This is a low-level WLAN firmware issue requiring patches from device/OEM manufacturers rather than application-level remediation.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA8.0 h
80.0 hours of engineering $13,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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