CVE-2025-47342

7.1 HIGH

📋 TL;DR

This vulnerability allows a denial-of-service condition in Qualcomm hardware when multiple profiles run concurrently with QHS (Qualcomm High-Speed) enabled. It affects devices using vulnerable Qualcomm chipsets, potentially causing temporary service disruption. The impact is limited to availability rather than data compromise.

💻 Affected Systems

Products:
  • Qualcomm chipsets with QHS capability
Versions: Specific versions not detailed in reference; check Qualcomm advisory
Operating Systems: Android, Linux-based systems using affected chipsets
Default Config Vulnerable: ⚠️ Yes
Notes: Requires QHS enabled and multi-profile concurrency scenarios

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system crash requiring hard reboot, disrupting all services on affected device

🟠

Likely Case

Temporary service degradation or application crashes until system recovers

🟢

If Mitigated

Minor performance impact with quick automatic recovery

🌐 Internet-Facing: MEDIUM - Could be triggered remotely if attacker can induce multi-profile concurrency
🏢 Internal Only: MEDIUM - Internal users or processes could trigger the condition

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Requires ability to trigger specific multi-profile concurrency conditions

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check Qualcomm October 2025 security bulletin

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

Restart Required: Yes

Instructions:

1. Check device manufacturer for firmware updates
2. Apply Qualcomm-provided patches through OEM updates
3. Reboot device after update

🔧 Temporary Workarounds

Disable QHS feature

all

Turn off Qualcomm High-Speed feature if not required

Device-specific; check manufacturer documentation

Limit concurrent profiles

all

Restrict multi-profile operations through policy

Configuration dependent on device management system

🧯 If You Can't Patch

  • Isolate affected devices from critical services
  • Implement monitoring for DoS symptoms and establish recovery procedures

🔍 How to Verify

Check if Vulnerable:

Check chipset version against Qualcomm advisory; examine if QHS is enabled in system configuration

Check Version:

Device-specific; typically 'getprop' or manufacturer diagnostic commands

Verify Fix Applied:

Verify firmware version matches patched version from manufacturer; test multi-profile operations

📡 Detection & Monitoring

Log Indicators:

  • Unexpected system reboots
  • Kernel panic logs
  • QHS-related error messages

Network Indicators:

  • Sudden service unavailability
  • Increased timeout errors

SIEM Query:

Search for 'kernel panic' OR 'system crash' OR 'QHS error' in system logs

🔗 References

📤 Share & Export