dbcve.org
Aqt1000 FirmwareOperating system · Qualcomm

CVE-2022-33263

HIGH · 7.8 CVSS v3.1 Published 2023-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 use after free in Core when multiple DCI clients register and deregister.

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 use-after-free vulnerability exists in the Core component where memory corruption occurs when multiple DCI clients perform registration and deregistration operations. The vulnerability stems from improper memory lifecycle management during concurrent client registration/deregistration events, allowing freed memory to be accessed after being returned to the allocator.

MitigationImplement proper reference counting or ownership tracking for DCI client objects to ensure memory is not freed while still in use. Add synchronization primitives to prevent race conditions between registration/deregistration operations and ensure all pointers are nullified immediately after freeing associated memory.

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
Wcn3991 FirmwareOperating system
Affected:all versions
Wcn3998 FirmwareOperating system
Affected:all versions
Wcn6750 FirmwareOperating system
Affected:all versions
Wcn685x 5 FirmwareOperating system
Affected:all versions
Wcn685x 1 FirmwareOperating system
Affected:all versions
Wcn785x 1 FirmwareOperating system
Affected:all versions
Wcn785x 5 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 chipset model in your device
    Check system information or device specifications to determine if the device uses one of the affected Qualcomm chipsets (Aqt1000, Wcn3991, Wcn3998, Wcn6750, Wcn685x, or Wcn785x). This may be found in /proc/cpuinfo, lsusb, dmesg, or device documentation.
    Affected if The device contains any of the listed Qualcomm chipset models (Aqt1000, Wcn3991, Wcn3998, Wcn6750, Wcn685x 1/5, or Wcn785x 1/5).
  2. Check the firmware version of the Qualcomm chipset
    Retrieve the firmware version using chipset-specific commands (such as 'atfwd --version', 'diag version', or vendor-specific tools) or by reading firmware version files in /firmware or /vendor/firmware. Compare against the affected version ranges listed.
    Affected if The firmware version falls within the affected ranges or, per the advisory, if the device uses any version of the listed firmware (the advisory lists 'all versions' for each product).
  3. Verify if DCI (Diagnostic Control Interface) feature is enabled
    Check system logs, kernel configuration, or runtime settings to determine whether the DCI client interface is active. This may involve checking /dev/diag, looking for 'DCI' in logcat output, or examining relevant kernel module加载 status.
    Affected if DCI feature is enabled and accessible on the device, as the vulnerability requires DCI client registration/deregistration operations to trigger.
  4. Look for crash logs or memory corruption indicators related to DCI operations
    Search system logs (dmesg, logcat, /var/log/messages) for crash reports, use-after-free errors, or memory corruption that mention DCI, client registration, or client deregistration. Look for symptoms like 'UAF', 'use after free', 'memory corruption', or 'NULL pointer' in conjunction with DCI-related messages.
    Affected if Crash logs or memory corruption events are found that correlate with DCI client operations, indicating potential exploitation of this vulnerability.

If the device uses any of the listed Qualcomm chipset firmware versions with DCI enabled and exhibits crashes or memory corruption during DCI client registration/deregistration, the environment is likely affected by CVE-2022-33263.

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

Implement proper reference counting or ownership tracking for DCI client objects to ensure memory is not freed while still in use. Add synchronization primitives to prevent race conditions between registration/deregistration operations and ensure all pointers are nullified immediately after freeing associated memory.

Fix this in Aqt1000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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