dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2022-33239

HIGH · 7.5 CVSS v3.1 Published 2022-11-15
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 DOS due to loop with unreachable exit condition in WLAN firmware while parsing IPV6 extension header. 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 · high confidence

A denial of service vulnerability exists in Qualcomm WLAN firmware where parsing IPv6 extension headers triggers an infinite loop with an unreachable exit condition. When malformed or crafted IPv6 packets with extension headers are received, the firmware enters an endless loop causing device hang or crash requiring restart.

MitigationApply vendor firmware updates from device/OEM manufacturers once available. Until then, consider disabling WLAN on affected devices or restricting network exposure to trusted sources, as exploitation requires delivery of malicious IPv6 packets to the target device.

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
Apq8096au FirmwareOperating system
Affected:all versions
Aqt1000 FirmwareOperating system
Affected:all versions
Ar8031 FirmwareOperating system
Affected:all versions
Ar8035 FirmwareOperating system
Affected:all versions
Csr8811 FirmwareOperating system
Affected:all versions
Csra6620 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
    Use commands such as `lspci -v`, `lsusb`, or check device/system documentation to enumerate the wireless chipset. Look for model numbers Apq8009, Apq8017, Apq8096au, Aqt1000, Ar8031, Ar8035, Csr8811, or Csra6620.
    Affected if The device uses any of the affected Qualcomm chipset models listed in the CVE.
  2. Determine the installed WLAN firmware version
    Check the firmware file or driver information. On Linux, use `iw`, `ethtool`, or inspect firmware files in `/lib/firmware/` or `/etc/firmware/` related to the wireless interface. Look for firmware version strings or build dates.
    Affected if The chipset matches an affected model and firmware version cannot be determined or is older than available patches.
  3. Verify WLAN interface is enabled and active
    Run `ip link show` or `iwconfig` to list wireless interfaces and their status. Confirm the WLAN interface is UP and has an IP address assigned.
    Affected if The WLAN interface is enabled and processing network traffic, making it reachable to receive malicious IPv6 packets.
  4. Confirm IPv6 is enabled on the WLAN interface
    Run `ip -6 addr show` or `cat /proc/sys/net/ipv6/conf/wlan*/disable_ipv6` to check if IPv6 is active on the wireless interface.
    Affected if IPv6 is enabled on the WLAN interface, as the vulnerability is triggered specifically by malformed IPv6 packets with extension headers.
  5. Assess network exposure of WLAN interface
    Review firewall rules (`iptables -L -n` or `ip6tables -L -n`), network configuration, and access controls to determine if the WLAN interface is directly exposed to untrusted networks or the internet.
    Affected if The WLAN interface is accessible to untrusted sources, allowing delivery of crafted malicious IPv6 packets to trigger the infinite loop.

A user is affected if their device contains any of the listed Qualcomm chipsets (Apq8009, Apq8017, Apq8096au, Aqt1000, Ar8031, Ar8035, Csr8811, Csra6620) with WLAN enabled and IPv6 active, and the WLAN interface is reachable to receive malicious IPv6 packets.

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 firmware updates from device/OEM manufacturers once available. Until then, consider disabling WLAN on affected devices or restricting network exposure to trusted sources, as exploitation requires delivery of malicious IPv6 packets to the target device.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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