dbcve.org
Apq8017 FirmwareOperating system · Qualcomm

CVE-2022-33299

HIGH · 7.5 CVSS v3.1 Published 2023-01-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Transient DOS due to null pointer dereference in Bluetooth HOST while receiving an attribute protocol PDU with zero length data.

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 null pointer dereference vulnerability exists in the Bluetooth HOST stack when processing Attribute Protocol (ATT) PDUs containing zero-length data. When an attacker sends a crafted ATT PDU with zero-length data, the Bluetooth host attempts to dereference a null pointer, causing a transient denial of service condition.

MitigationApply vendor-provided patches for the Bluetooth stack that include proper null pointer validation before dereferencing ATT PDU data fields. If no patch is available, consider network-level controls to limit Bluetooth exposure.

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
Apq8017 FirmwareOperating system
Affected:all versions
Apq8096au FirmwareOperating system
Affected:all versions
Ar8031 FirmwareOperating system
Affected:all versions
Csra6620 FirmwareOperating system
Affected:all versions
Csra6640 FirmwareOperating system
Affected:all versions
Csrb31024 FirmwareOperating system
Affected:all versions
Mdm9150 FirmwareOperating system
Affected:all versions
Mdm9206 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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Qualcomm chipset model
    Determine the specific Qualcomm chip present in your device or system (examples include Apq8017, Apq8096au, Ar8031, Csra6620, Csra6640, Csrb31024, Mdm9150, or Mdm9206). This may be listed in system documentation, hardware specifications, or via commands like 'lspci', 'lsusb', or probing /proc/cpuinfo on embedded devices.
    Affected if The device uses any of the listed affected chipsets (Apq8017, Apq8096au, Ar8031, Csra6620, Csra6640, Csrb31024, Mdm9150, or Mdm9206)
  2. Confirm Bluetooth is enabled
    Check whether Bluetooth functionality is active on the system. This can be done via system service status (systemctl/status bluedroid/bluez), checking Bluetooth adapter state (hciconfig or btmgmt commands), or verifying /sys/class/bluetooth/ entries exist and show powered-on state.
    Affected if Bluetooth is enabled and the system can process incoming Bluetooth connections or ATT protocol traffic
  3. Verify the Bluetooth host stack is running
    Inspect running processes for Bluetooth host stack daemons (such as bluetoothd, bluedroid, or vendor-specific Bluetooth services). Use commands like 'ps aux | grep -i blue' or check service status via the system's service manager.
    Affected if The Bluetooth host stack daemon is actively running and processing Bluetooth protocol messages including ATT PDUs
  4. Review system logs for null pointer dereference crashes
    Search system logs (dmesg, journalctl, /var/log/messages, or vendor-specific log locations) for crash entries, kernel panics, or Bluetooth-related errors mentioning 'null pointer', 'dereference', 'ATT', or 'bluetooth' during the time of suspected exploitation or at any time.
    Affected if Logs contain crash entries indicating null pointer dereference in the Bluetooth stack related to ATT PDU processing
  5. Check for unapplied Bluetooth firmware patches
    Compare the installed Bluetooth firmware version against vendor release notes or security advisories for CVE-2022-33299. Check firmware version via vendor-specific tools, /etc/firmware paths, or by querying the Bluetooth controller for LMP version information.
    Affected if The installed firmware version for the affected chipset has not been patched to address the null pointer dereference vulnerability in ATT PDU handling

You are affected if your device uses one of the listed Qualcomm chipsets (Apq8017, Apq8096au, Ar8031, Csra6620, Csra6640, Csrb31024, Mdm9150, or Mdm9206) with Bluetooth enabled and the vendor patch for CVE-2022-33299 has not been applied.

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-provided patches for the Bluetooth stack that include proper null pointer validation before dereferencing ATT PDU data fields. If no patch is available, consider network-level controls to limit Bluetooth exposure.

Fix this in Apq8017 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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