CVE-2025-47370
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 when a remote device sends an invalid connection request during BT connectable LE scan.
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 transient denial-of-service vulnerability exists in the Bluetooth stack where a remote device sending an invalid connection request during a connectable Low Energy (LE) scan can cause the scanning device to become unresponsive or crash. The vulnerability stems from improper handling of malformed connection parameters in the LE scanning state.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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 Bluetooth firmware or chip modelCheck system information or Bluetooth adapter details to determine if the device uses a Qualcomm chip (Ar8035, Csrb31024, Fastconnect 6700/6900/7800, Sm8550p, Sm8635, Sm8635p). This may appear in lspci, lsusb, hcitool, or system Bluetooth settings.Affected if The device contains any of the listed Qualcomm components (Ar8035, Csrb31024, Fastconnect 6700, Fastconnect 6900, Fastconnect 7800, Sm8550p, Sm8635, or Sm8635p firmware).
-
Determine if Bluetooth LE scanning is activeUse Bluetooth management tools (such as hciconfig, btmgmt, or bluetoothctl) to check if the device is currently performing LE scans. Look for scan states like 'LE scan' or 'connectable' in the output.Affected if Bluetooth LE scanning is currently enabled or was recently active on the device.
-
Review system logs for Bluetooth-related crashesExamine system logs (journalctl, dmesg, or /var/log/syslog) for entries related to Bluetooth crashes, freezes, or unexpected behavior, particularly those mentioning malformed packets, connection parameters, or LE scan state failures.Affected if Logs show Bluetooth stack crashes, unexpected resets, or 'bluetoothd' or 'hci' errors coinciding with LE scanning activity.
-
Check for vendor firmware versionQuery the Bluetooth controller firmware version using commands like hciconfig -a, btmgmt info, or manufacturer-specific tools. Compare against known affected version ranges.Affected if The firmware version matches the affected products listed (all versions of Ar8035, Csrb31024, Fastconnect 6700/6900/7800, Sm8550p, Sm8635, Sm8635p).
A user is affected if their device contains any of the listed Qualcomm Bluetooth firmware chips and has Bluetooth LE scanning enabled, as the vulnerability requires the scanning state to trigger the malformed connection parameter handling flaw.
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 security patches for the Bluetooth stack firmware/software. Until patches are available, limit Bluetooth usage in public or untrusted environments and disable Bluetooth when not actively needed.
- Consultation3.0 h
- Implementation8.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 $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47370 — 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-2025-47370 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