dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2022-25749

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
Transient Denial-of-Service in WLAN due to buffer over-read while parsing MDNS 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

A buffer over-read vulnerability exists in the WLAN subsystem when parsing MDNS (Multicast DNS) frames. An attacker sending specially crafted MDNS frames can trigger the buffer over-read, causing a transient denial-of-service condition. The vulnerability affects multiple Snapdragon chip families used in mobile devices, IoT products, wearables, and infrastructure equipment.

MitigationApply vendor-supplied firmware/security updates for affected Snapdragon components. Until patches are available, consider disabling MDNS functionality in WLAN configurations or implementing network-level filtering of MDNS traffic.

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

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 chipset model
    Check the device specifications, system information, or boot logs for the Qualcomm APQ model number (Apq8009, Apq8017, Apq8064au, Apq8076, Apq8096au, Aqt1000, Ar8031, or Ar8035). This may be visible in /proc/cpuinfo, device datasheets, or firmware banners.
    Affected if The device uses any of the listed Qualcomm APQ variants (Apq8009, Apq8017, Apq8064au, Apq8076, Apq8096au, Aqt1000, Ar8031, Ar8035).
  2. Check if WLAN interface is active
    Run 'ip link show' or 'iwconfig' to list wireless network interfaces. Verify if any WLAN interface (such as wlan0) exists and is in an UP or UNKNOWN state.
    Affected if A WLAN interface is present and active, as the vulnerability exists in the WLAN subsystem parsing MDNS frames.
  3. Verify MDNS processing is enabled
    Check if the device is configured to process MDNS (Multicast DNS) traffic. This may be visible in network configuration files, firewall rules (iptables -L), or WLAN driver parameters. Look for mdns, avahi, or port 5353 configurations.
    Affected if MDNS functionality is enabled in the WLAN or network stack, allowing the device to parse incoming MDNS frames.
  4. Inspect WLAN firmware version
    If accessible, query the WLAN firmware version through debug interfaces, vendor tools, or by reading firmware version files in /sys or /proc (e.g., /sys/class/net/wlan0/firmware_version).
    Affected if The firmware version matches one of the affected chip families and all versions are considered vulnerable per the advisory.

The device is likely affected if it uses any of the listed Qualcomm APQ/AR chipsets (all versions) and has WLAN functionality enabled with MDNS processing 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 vendor-supplied firmware/security updates for affected Snapdragon components. Until patches are available, consider disabling MDNS functionality in WLAN configurations or implementing network-level filtering of MDNS traffic.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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