CVE-2025-47370

6.5 MEDIUM

📋 TL;DR

This vulnerability allows a remote attacker to cause a denial of service (DoS) by sending invalid Bluetooth Low Energy (LE) connection requests during a connectable scan. It affects devices with Qualcomm Bluetooth chipsets that are performing LE scans. The attack disrupts Bluetooth functionality temporarily but doesn't compromise data or allow code execution.

💻 Affected Systems

Products:
  • Qualcomm Bluetooth chipsets
Versions: Specific versions not publicly detailed; refer to Qualcomm November 2025 security bulletin
Operating Systems: Android, Linux-based IoT devices, embedded systems using Qualcomm Bluetooth
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects devices performing Bluetooth LE connectable scans. Devices not using LE scanning or with Bluetooth disabled are not vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Permanent Bluetooth radio failure requiring device reboot, disrupting all Bluetooth-dependent services including medical devices, payment systems, or industrial controls.

🟠

Likely Case

Temporary Bluetooth service disruption lasting seconds to minutes, causing dropped connections and requiring manual reconnection of paired devices.

🟢

If Mitigated

Minor service interruption with automatic recovery within seconds, minimal user impact.

🌐 Internet-Facing: LOW - Requires physical proximity (Bluetooth range) and specific timing during LE scans.
🏢 Internal Only: MEDIUM - Internal attackers with physical access could disrupt Bluetooth services in sensitive environments like hospitals or industrial facilities.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: MEDIUM

Requires attacker to be within Bluetooth range (typically <100m) and send malformed packets during specific scan windows. Timing is critical.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Refer to Qualcomm November 2025 security bulletin for specific firmware versions

Vendor Advisory: https://docs.qualcomm.com/product/publicresources/securitybulletin/november-2025-bulletin.html

Restart Required: Yes

Instructions:

1. Check device manufacturer for firmware updates. 2. Apply Qualcomm-provided Bluetooth firmware patch. 3. Reboot device. 4. Verify Bluetooth functionality.

🔧 Temporary Workarounds

Disable Bluetooth LE scanning

all

Prevents the vulnerable state by disabling connectable LE scans

# Android: adb shell settings put global bluetooth_le_scan_mode 0
# Linux: hciconfig hci0 noscan

Reduce Bluetooth visibility

all

Set Bluetooth to non-discoverable mode to limit scan exposure

# Android: adb shell settings put global bluetooth_discoverability 0
# Linux: hciconfig hci0 piscan

🧯 If You Can't Patch

  • Disable Bluetooth when not in use, especially in high-risk environments
  • Implement physical security controls to limit Bluetooth range access

🔍 How to Verify

Check if Vulnerable:

Check if device uses Qualcomm Bluetooth and performs LE scans: 'hciconfig -a' on Linux or check Bluetooth settings on Android

Check Version:

# Linux: hciconfig -a | grep Firmware
# Android: getprop | grep bluetooth

Verify Fix Applied:

Verify Bluetooth firmware version matches patched version from Qualcomm bulletin and test LE scanning functionality

📡 Detection & Monitoring

Log Indicators:

  • Bluetooth stack crashes
  • LE scan failures
  • Connection request errors in Bluetooth logs

Network Indicators:

  • Unusual Bluetooth LE connection attempts from unknown MAC addresses
  • Malformed Bluetooth packets

SIEM Query:

source="bluetooth_logs" AND ("LE scan failed" OR "connection request invalid")

🔗 References

📤 Share & Export