CVE-2022-33290
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 in Bluetooth HOST due to null pointer dereference when a mismatched argument is passed.
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 null pointer dereference vulnerability in the Bluetooth HOST stack allows an attacker to cause a transient denial of service by passing a mismatched argument. When the HOST receives an unexpected or malformed argument, it attempts to dereference a null pointer, leading to a crash or hang. This affects the Bluetooth communication capability until the service is restarted.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 hardware or firmware modelCheck the system information or bootloader/firmware version strings to determine if the device uses any of the following chipset families: Apq8017, Apq8096au, Ar8031, Csra6620, Csra6640, Csrb31024, Mdm9150, or Mdm9206Affected if The hardware/firmware matches any of the listed Qualcomm chipset families (Apq8017, Apq8096au, Ar8031, Csra6620, Csra6640, Csrb31024, Mdm9150, Mdm9206)
-
Confirm Bluetooth stack is presentInspect the system for Bluetooth HOST stack components or services. On Linux systems this may involve checking for bluetoothd, hcid, or similar Bluetooth daemon processes and librariesAffected if A Bluetooth HOST stack implementation is running on the system
-
Verify Bluetooth is actively usedCheck if Bluetooth interfaces are configured or active (for example, running 'hciconfig' or 'btmgmt' on Linux, or checking Bluetooth manager service status)Affected if Bluetooth interfaces are enabled or paired devices exist, indicating active Bluetooth usage
-
Review Bluetooth HOST argument handlingInspect Bluetooth HOST stack configuration or logs for evidence of argument validation routines. Check for any crash dumps, kernel panics, or service failure logs related to Bluetooth argument processingAffected if The system experiences crashes or hangs when Bluetooth receives malformed data, or if logs show null pointer dereferences in Bluetooth HOST code
The environment is affected if the system runs any of the listed Qualcomm firmware variants (Apq8017, Apq8096au, Ar8031, Csra6620, Csra6640, Csrb31024, Mdm9150, Mdm9206) with the Bluetooth HOST stack enabled and actively processing Bluetooth communications.
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-provided patches for the Bluetooth stack. Implement input validation and null-pointer checks in the Bluetooth HOST argument handling code to prevent dereferencing of uninitialized or mismatched pointers.
- Consultation2.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33290 — 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-33290 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