CVE-2022-25710
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 · uneditedDenial of service due to null pointer dereference when GATT is disconnected 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 confidenceA null pointer dereference vulnerability exists in the Bluetooth GATT disconnect handling code in multiple Qualcomm Snapdragon chipset families. When a GATT connection is terminated, the code fails to properly validate a pointer before dereferencing it, causing a kernel panic or system crash that results in denial of service.
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 Qualcomm chipset model in useCheck device specifications, system information, or bootloader/firmware identifiers to determine the exact Qualcomm chipset (e.g., Apq8009, Apq8017, Apq8096au, Ar8031, Csra6620, Csra6640, Csrb31024, Mdm9150)Affected if The chipset matches one of the listed affected models (Apq8009, Apq8017, Apq8096au, Ar8031, Csra6620, Csra6640, Csrb31024, Mdm9150)
-
Locate the Bluetooth firmware versionAccess the device's firmware or baseband information via manufacturer diagnostic tools, AT command interfaces, or system logs that expose Bluetooth subsystem version stringsAffected if Firmware version cannot be determined or the available firmware is from the affected product list (all versions)
-
Verify Bluetooth GATT functionality is activeCheck if Bluetooth is enabled and monitor for active GATT client or server connections using Bluetooth stack logs, hci tool dumps, or system monitoringAffected if Bluetooth is enabled and GATT connections are being established or terminated
-
Review system logs for GATT disconnect-related crashesExamine kernel logs, crash dumps, or system event logs for entries indicating null pointer dereferences, kernel panics, or unexpected Bluetooth stack failures occurring during connection terminationAffected if Logs show kernel panics or crashes with stack traces referencing GATT disconnect handlers or null pointer dereferences in the Bluetooth subsystem
A device is affected if it uses any of the listed Qualcomm chipset models and utilizes Bluetooth GATT functionality, as all firmware versions of these chipsets contain the vulnerability in the GATT disconnect handling code.
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-supplied firmware updates from Qualcomm/OEM partners that address the GATT disconnection handler. Until patches are available, monitor for unexpected device resets or Bluetooth stack failures.
- Consultation4.0 h
- Implementation2.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 $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25710 — 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-25710 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