CVE-2022-40533
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 · uneditedTransient DOS due to untrusted Pointer Dereference in core while sending USB QMI request.
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 confidenceA denial of service vulnerability exists in the core component where an untrusted pointer is dereferenced during USB QMI (Qualcomm MSM Interface) request processing. This can cause a crash or transient interruption when a specially crafted USB QMI request triggers the vulnerable pointer dereference path.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Qualcomm chipset in your deviceCheck your device specifications, system information, or firmware documentation to determine if the chipset matches any of the following: Csra6620, Csra6640, Wcn3991, Wcn3998, Wcn6750, Qca6390, Wcn685x 5, or Wcn685x 1.Affected if The device uses any of the listed Qualcomm chipsets.
-
Check the firmware versionQuery the device firmware or system information for the installed version of the identified Qualcomm chipset firmware.Affected if The firmware version falls within the affected product ranges listed (all versions for each listed product).
-
Verify USB QMI interface is enabledCheck device configuration or system settings to determine whether the USB QMI (Qualcomm MSM Interface) functionality is active and accessible.Affected if USB QMI interface is enabled and processing requests.
-
Inspect system logs for USB QMI crashesReview system logs, kernel messages, or crash dumps for entries related to USB QMI request handling failures or unexpected resets.Affected if Logs show crashes or interruptions originating from USB QMI processing.
If your device uses any of the affected Qualcomm chipsets (Csra6620, Csra6640, Wcn3991, Wcn3998, Wcn6750, Qca6390, Wcn685x 5, or Wcn685x 1) with USB QMI enabled, and you process untrusted USB QMI requests, you are likely affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor patches for the core USB QMI handling component; until then, restrict or filter untrusted USB QMI requests to prevent triggering the vulnerable code path.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40533 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-40533 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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