dbcve.org
Aqt1000 FirmwareOperating system · Qualcomm

CVE-2022-33226

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 buffer copy without checking the size of input in Core while processing ioctl commands from diag client applications.

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 memory corruption vulnerability exists in the Core component where buffer copy operations lack proper size validation when processing ioctl commands from diag client applications. This allows an attacker to trigger a buffer overflow by sending specially crafted ioctl requests with oversized input buffers, potentially leading to arbitrary code execution or denial of service.

MitigationImplement bounds checking on all buffer copy operations within ioctl handlers, validate input size parameters before memory allocation or copying, and use safe memory copy functions that enforce buffer length limits.

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
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
Qam8255p 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 chip model
    Check the system hardware or device documentation for the chipset. Common methods: 'lspci' for PCIe devices, 'lsusb' for USB devices, or check /proc/cpuinfo on embedded devices. Look for identifiers: Aqt1000, Wcn3991, Wcn3998, Wcn685x, Wcn785x, or Qam8255p.
    Affected if The system uses any of the listed Qualcomm chips: Aqt1000, Wcn3991, Wcn3998, Wcn685x 5, Wcn685x 1, Wcn785x 1, Wcn785x 5, or Qam8255p.
  2. Verify the diag interface is accessible
    Check if the diag character device exists. On Linux, look for /dev/diag or /dev/mhi/diag. Also check lsmod for loaded diag-related kernel modules (diag, mhi_core). Run: 'ls -la /dev/diag' or 'ls -la /dev/mhi/diag'.
    Affected if The diag device interface is present and accessible, allowing ioctl communication with diag client applications.
  3. Check diag driver configuration
    Examine the diag driver configuration and permissions. Check /sys/class/mhi/ for MHI device directories. Look at /proc/mhi/status if available. Run: 'cat /proc/mhi/status' or check /sys/kernel/debug/mhi/ for MHI channel information.
    Affected if The diag MHI channel or driver is active and exposes ioctl command handling to userspace.
  4. Identify exposed diag client interfaces
    Check for diag client application interfaces that can send ioctl commands. Look in /dev/ for char devices related to diag. Check if any application has CAP_NET_RAW or CAP_SYS_RAWIO capabilities that could access diag. Run: 'ls -la /dev/*diag*' and review user/group permissions.
    Affected if Any userspace process or diagnostic tool can access the diag ioctl interface without proper isolation.

The environment is affected if it contains any of the listed Qualcomm firmware components (Aqt1000, Wcn3991, Wcn3998, Wcn685x, Wcn785x, Qam8255p) with an accessible diag interface that allows ioctl command injection.

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 bounds checking on all buffer copy operations within ioctl handlers, validate input size parameters before memory allocation or copying, and use safe memory copy functions that enforce buffer length limits.

Fix this in Aqt1000 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-33226 — 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-33226 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