dbcve.org
Sd 8 Gen1 5g FirmwareOperating system · Qualcomm

CVE-2022-33217

HIGH · 7.8 CVSS v3.1 Published 2022-10-19
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 Qualcomm IPC due to buffer copy without checking the size of input while starting communication with a compromised kernel. in Snapdragon Mobile

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

Memory corruption vulnerability in Qualcomm's Inter-Process Communication (IPC) mechanism within Snapdragon Mobile processors. The flaw stems from a buffer copy operation that fails to validate input size, leading to buffer overflow when initiating communication with a compromised kernel.

MitigationApply vendor-supplied firmware patches from Qualcomm through device OEM/carrier update channels; until patch availability, limit kernel attack surface and monitor for indicators of kernel compromise.

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
Sd 8 Gen1 5g FirmwareOperating system
Affected:all versions
Wcd9380 FirmwareOperating system
Affected:all versions
Wcn6855 FirmwareOperating system
Affected:all versions
Wcn6856 FirmwareOperating system
Affected:all versions
Wcn7850 FirmwareOperating system
Affected:all versions
Wcn7851 FirmwareOperating system
Affected:all versions
Wsa8830 FirmwareOperating system
Affected:all versions
Wsa8835 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 components in the device
    Use commands such as 'lspci', 'lsusb', or check /sys/devices/system for Qualcomm network, audio, or wireless components. For mobile devices, check device specifications or use apps like CPU-Z to identify the chipset and associated components (Wcd9380, Wcn6855, Wcn6856, Wcn7850, Wcn7851, Wsa8830, Wsa8835).
    Affected if Any of the listed Qualcomm firmware components (Wcd9380, Wcn6855, Wcn6856, Wcn7850, Wcn7851, Wsa8830, Wsa8835) or Snapdragon Sd 8 Gen1 5g are present in the device.
  2. Check firmware version of affected Qualcomm components
    For wireless/coexistence chips (Wcn series), check /vendor/firmware or use 'cat /sys/class/net/*/device/uevent' to locate firmware files. For audio codecs (Wcd, Wsa series), examine /vendor/firmware/ directory or use 'getprop' on Android devices. Compare the firmware file dates or version strings against known patch dates from the device OEM.
    Affected if The firmware version cannot be verified as patched OR the component firmware predates the vendor patch release date.
  3. Verify kernel integrity and IPC subsystem
    Check /proc/kallsyms, /proc/modules, or use 'cat /proc/keys' for unexpected or unsigned kernel modules. Examine dmesg logs for IPC-related errors or warnings. Use tools like 'aide' or 'tripwire' to detect unauthorized kernel modifications.
    Affected if Unauthorized kernel modules loaded, unexpected symbols in kernel space, or IPC-related error messages in kernel logs exist, indicating kernel compromise.
  4. Check OEM/carrier patch availability
    Research the device manufacturer website or carrier update notices for CVE-2022-33217 patch availability. For Android devices, check Security Patch Level in Settings > About Phone > Security Patch Level. Compare the patch date against the date when the CVE fix became available.
    Affected if No security update containing CVE-2022-33217 has been applied, or the Security Patch Level predates the vendor release date for this fix.

A device is affected if it contains any of the listed Qualcomm components (Sd 8 Gen1 5g, Wcd9380, Wcn6855, Wcn6856, Wcn7850, Wcn7851, Wsa8830, Wsa8835) and has not received a vendor-supplied firmware patch for CVE-2022-33217.

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 patches from Qualcomm through device OEM/carrier update channels; until patch availability, limit kernel attack surface and monitor for indicators of kernel compromise.

Fix this in Sd 8 Gen1 5g Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation2.0 h
  • Testing16.0 h
  • Review / QA8.0 h
34.0 hours of engineering $5,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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