dbcve.org
Aqt1000 FirmwareOperating system · Qualcomm

CVE-2022-33227

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 in Linux android due to double free while calling unregister provider after register call.

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 double-free vulnerability exists in the Linux Android kernel's provider registration mechanism. When a provider is registered and then unregistered via the unregister function, the memory allocated for the provider is freed twice, leading to memory corruption that can be exploited for local privilege escalation.

MitigationApply the vendor-supplied kernel security patch for CVE-2022-33227, which corrects the reference counting or memory management logic in the provider unregister path to prevent the double-free condition.

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
Csrb31024 FirmwareOperating system
Affected:all versions
Wcn3991 FirmwareOperating system
Affected:all versions
Wcn3998 FirmwareOperating system
Affected:all versions
Qca6390 FirmwareOperating system
Affected:all versions
Wcn685x 5 FirmwareOperating system
Affected:all versions
Wcn685x 1 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 Qualcomm firmware components
    Examine system information or firmware tables to determine if any of the following Qualcomm components are present: Aqt1000, Csrb31024, Wcn3991, Wcn3998, Qca6390, Wcn685x (including Wcn685x 5 and Wcn685x 1 variants), or Qam8255p. Use commands like 'dmesg', 'cat /proc/firmware', or vendor-specific tools to list loaded firmware modules.
    Affected if Any of the listed Qualcomm firmware components are present in the system, as all versions of these products are vulnerable.
  2. Locate firmware version information
    Query the specific firmware component for its version string. For wireless chips (Wcn3991, Wcn3998, Wcn685x), check via 'iw list' or similar wireless tools. For other components, use vendor diagnostic interfaces or check /firmware or /vendor/firmware directories for version metadata.
    Affected if A firmware version can be retrieved, confirming the presence of the affected component (all versions are vulnerable).
  3. Verify kernel provider registration module
    Check if the kernel loads or exposes the provider registration mechanism. This may be visible in kernel logs, module lists (lsmod), or by examining /sys/kernel/debug or /proc entries related to provider or service registration.
    Affected if The kernel provider registration interface is active or loadable, which is required for the double-free to trigger.
  4. Confirm vulnerable code path usage
    Monitor for events involving provider registration and unregistration in the kernel. Search logs or trace events for calls to provider register/unregister functions. The vulnerability triggers when a provider is registered and then unregistered.
    Affected if The system has ever registered and unregistered a provider through the affected kernel mechanism, exposing the double-free condition.

If the device contains any of the affected Qualcomm firmware components (Aqt1000, Csrb31024, Wcn3991, Wcn3998, Qca6390, Wcn685x, Qam8255p) and uses the kernel provider registration feature, the double-free vulnerability is present since all versions of these firmware products are affected.

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 the vendor-supplied kernel security patch for CVE-2022-33227, which corrects the reference counting or memory management logic in the provider unregister path to prevent the double-free condition.

Fix this in Aqt1000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing16.0 h
  • Review / QA8.0 h
36.0 hours of engineering $6,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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