CVE-2024-45559

5.5 MEDIUM

📋 TL;DR

This vulnerability allows a denial-of-service (DoS) condition in Qualcomm's GVM (Guest Virtual Machine) when it sends a specific message type to the Vdev-FastRPC backend. It affects systems using Qualcomm chipsets with vulnerable GVM implementations. The impact is limited to temporary service disruption rather than data compromise.

💻 Affected Systems

Products:
  • Qualcomm chipsets with GVM and Vdev-FastRPC implementations
Versions: Specific versions not publicly detailed; refer to Qualcomm January 2025 bulletin
Operating Systems: Android, Linux-based systems using affected Qualcomm chipsets
Default Config Vulnerable: ⚠️ Yes
Notes: Requires GVM functionality to be enabled and accessible; exact chipset models not specified in public advisory.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete denial-of-service for affected virtualized services, causing system instability and requiring reboot.

🟠

Likely Case

Temporary service disruption affecting specific GVM functions, potentially causing application crashes.

🟢

If Mitigated

Minimal impact with proper isolation and monitoring; service may recover automatically.

🌐 Internet-Facing: LOW - Requires local access to GVM interface, not typically internet-exposed.
🏢 Internal Only: MEDIUM - Could be exploited by malicious insiders or compromised internal systems with GVM access.

🎯 Exploit Status

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

Exploitation requires ability to send specific messages to GVM backend; likely requires some level of system access.

🛠️ Fix & Mitigation

✅ Official Fix

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

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

Restart Required: Yes

Instructions:

1. Check Qualcomm advisory for affected chipset models. 2. Obtain updated firmware from device manufacturer. 3. Apply firmware update following manufacturer instructions. 4. Reboot system.

🔧 Temporary Workarounds

Disable GVM functionality

linux

If GVM features are not required, disable them to eliminate attack surface

Specific commands vary by device; consult manufacturer documentation

Restrict GVM access

linux

Limit which processes/users can interact with GVM interfaces

Use SELinux/AppArmor policies to restrict GVM access

🧯 If You Can't Patch

  • Implement strict access controls to GVM interfaces
  • Monitor system logs for unusual GVM message patterns

🔍 How to Verify

Check if Vulnerable:

Check chipset model and firmware version against Qualcomm advisory; no simple public detection command available

Check Version:

cat /proc/cpuinfo | grep -i qualcomm (for chipset identification); firmware version check varies by device

Verify Fix Applied:

Verify firmware version has been updated to patched version specified in Qualcomm bulletin

📡 Detection & Monitoring

Log Indicators:

  • Unusual GVM message patterns
  • System crashes or reboots related to GVM services

Network Indicators:

  • Not network exploitable; local system issue

SIEM Query:

Search for GVM-related error messages or service disruptions in system logs

🔗 References

📤 Share & Export