dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2022-25651

CRITICAL · 9.8 CVSS v3.1 Published 2022-06-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Memory corruption in bluetooth host due to integer overflow while processing BT HFP-UNIT profile in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music

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 memory corruption vulnerability exists in the Bluetooth host stack of Qualcomm Snapdragon processors due to an integer overflow when processing the BT HFP-UNIT (Hands-Free Profile) profile. The overflow allows attackers to trigger memory corruption potentially leading to remote code execution or denial of service.

MitigationApply vendor-supplied firmware/security patches from Qualcomm and device manufacturers. Until patches are available, limit Bluetooth exposure and disable HFP functionality where possible.

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
Apq8009 FirmwareOperating system
Affected:all versions
Apq8017 FirmwareOperating system
Affected:all versions
Apq8053 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

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 the Qualcomm chipset model
    Check the device specifications, system information, or Bluetooth adapter details to determine the exact Qualcomm chipset (e.g., Apq8009, Apq8017, Apq8053, Apq8096au, Ar8031, Csra6620, Csra6640, or Csrb31024). On Linux, this may appear in 'hciinfo' or '/proc/cpuinfo'. On Android, check 'Settings > About Phone > Baseband' or use 'getprop' commands.
    Affected if The chipset matches any of the listed affected models: Apq8009, Apq8017, Apq8053, Apq8096au, Ar8031, Csra6620, Csra6640, or Csrb31024.
  2. Verify Bluetooth is enabled
    Check whether Bluetooth is turned on in the device settings or via system commands (e.g., 'hciconfig' on Linux, or Bluetooth settings on Android).
    Affected if Bluetooth is currently enabled on the device.
  3. Determine if HFP (Hands-Free Profile) is in use
    Check active Bluetooth connections and profiles. On Linux, use 'bluetoothctl info' or 'sdptool browse' to list active profiles. Look for HFP-AG (Audio Gateway) or HFP-HF (Hands-Free) profile connections. On Android, check paired device profiles in Bluetooth settings.
    Affected if Any Bluetooth device is connected using the HFP profile, or HFP-AG/HFP-HF functionality is active on the host stack.
  4. Check Bluetooth firmware version
    Query the Bluetooth controller firmware version using vendor-specific tools (e.g., 'hciconfig -v', 'btmon', or manufacturer-provided diagnostic tools). Compare the firmware version against any vendor release notes.
    Affected if The Bluetooth firmware version is unpatched and the device uses an affected chipset with Bluetooth and HFP enabled.

A device is affected if it uses any of the listed Qualcomm chipsets (Apq8009, Apq8017, Apq8053, Apq8096au, Ar8031, Csra6620, Csra6640, Csrb31024) with Bluetooth enabled and the HFP profile active or connectable.

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/security patches from Qualcomm and device manufacturers. Until patches are available, limit Bluetooth exposure and disable HFP functionality where possible.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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