CVE-2022-22105
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 · uneditedMemory corruption in bluetooth due to integer overflow while processing HFP-UNIT profile in Snapdragon Auto, Snapdragon Consumer 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 confidenceMemory corruption vulnerability in the Bluetooth stack caused by an integer overflow while processing the HFP-UNIT (Hands-Free Profile) profile. This flaw allows remote attackers to trigger memory corruption via specially crafted Bluetooth packets, potentially leading to code execution on affected Snapdragon Auto, Consumer IOT, Mobile, and Voice & Music platforms.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Qualcomm chipset modelCheck the device specifications, system information, or firmware metadata to determine if the chipset is one of: Apq8009, Apq8017, Apq8053, Apq8096au, Ar8031, Csra6620, Csra6640, or Csrb31024Affected if The chipset matches any of the affected models listed in the CVE
-
Confirm Bluetooth is enabledCheck the device Bluetooth settings, status, or runtime configuration to verify Bluetooth functionality is activeAffected if Bluetooth is turned on and actively functioning
-
Verify HFP (Hands-Free Profile) support is availableCheck Bluetooth profile configuration or examine which profiles are enabled; HFP is typically used for hands-free calling, car kits, and audio gatewaysAffected if HFP profile is loaded, registered, or available on the Bluetooth stack
-
Check if HFP is actively in useInspect active Bluetooth connections, pairing records, or profile usage logs to see if any HFP connection (such as a phone call or audio streaming) has occurredAffected if HFP has been connected or is currently active
-
Review firmware version if determinableQuery the device or firmware for version information via diagnostic ports, bootloader information, or vendor documentationAffected if The firmware version cannot be determined or is any version (all versions of affected chipsets are vulnerable)
If the device uses an affected Qualcomm chipset (Apq8009, Apq8017, Apq8053, Apq8096au, Ar8031, Csra6620, Csra6640, or Csrb31024) and has Bluetooth with HFP enabled, the environment is 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 Qualcomm firmware/security patches from device manufacturers; until patches are available, reduce Bluetooth exposure and disable HFP functionality if possible.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22105 — 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-22105 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