Aqt1000 FirmwareOperating system · Qualcomm

CVE-2022-40514

CRITICAL · 9.8 CVSS v3.1 Published 2023-02-12
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 due to buffer copy without checking the size of input in WLAN Firmware while processing CCKM IE in reassoc response frame.

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

Buffer overflow vulnerability in WLAN firmware where processing a CCKM IE (Cisco Centralized Key Management) in a reassoc response frame copies data to a buffer without validating the input size, leading to memory corruption.

MitigationApply vendor-supplied firmware update addressing the buffer overflow in WLAN firmware; until patched, restrict wireless network access to trusted devices to reduce exposure.

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
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 Qualcomm wireless chipset model
    Run commands such as 'lspci -v' for PCIe无线 adapters, 'iw list' for Linux wireless drivers, or check device documentation to identify the specific Qualcomm chip (Aqt1000, Ar8031, Ar8035, Ar9380, Csr8811, Csra6620, Csra6640, or Csrb31024)
    Affected if The device uses any of the eight affected Qualcomm chips listed in the CVE
  2. Determine firmware version of the wireless chipset
    Use vendor-specific tools or check /proc/ath10k_version, /sys/firmware/efi/efivars (for ath10k), or run 'ethtool -i wlan0' to retrieve firmware version details; consult device management interface for embedded devices
    Affected if The installed firmware version matches any of the affected products (Aqt1000, Ar8031, Ar8035, Ar9380, Csr8811, Csra6620, Csra6640, Csrb31024) - all versions are affected
  3. Verify if CCKM is enabled
    Check wireless controller or AP configuration for Centralized Key Management settings; run 'iw dev wlan0 info' and review security settings, or access the wireless infrastructure management console to inspect 802.11r/CCKM settings
    Affected if CCKM (Cisco Centralized Key Management) is configured or enabled on the wireless client or AP
  4. Confirm device processes reassoc response frames
    Monitor wireless traffic with tcpdump -i wlan0 -w capture.pcap 'wlan.fc.type==0 and wlan.fc.subtype==1' or check AP logs for reassoc response processing; verify the device acts as a wireless client connecting to WPA2-Enterprise networks
    Affected if The device is a wireless client that processes reassoc response frames from an AP, particularly in enterprise WPA2 environments

A user is affected if their environment contains any of the eight listed Qualcomm wireless chipsets (Aqt1000, Ar8031, Ar8035, Ar9380, Csr8811, Csra6620, Csra6640, Csrb31024) with CCKM enabled and the ability to process reassoc response frames, since all firmware versions of these chips 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-supplied firmware update addressing the buffer overflow in WLAN firmware; until patched, restrict wireless network access to trusted devices to reduce exposure.

Fix this in Aqt1000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-40514 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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