CVE-2024-43064

7.5 HIGH

📋 TL;DR

This CVE describes a denial-of-service vulnerability in Qualcomm System Memory Management Unit (SMMU) where uncontrolled resource consumption occurs when drivers, applications, or SMMU clients access global registers. The vulnerability allows attackers to cause system instability or crashes by exhausting SMMU resources. It affects devices using vulnerable Qualcomm chipsets.

💻 Affected Systems

Products:
  • Qualcomm chipsets with vulnerable SMMU implementations
Versions: Specific versions not publicly detailed; refer to Qualcomm advisory for affected chipsets.
Operating Systems: Android, Linux-based systems using affected Qualcomm hardware
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability is hardware/firmware based; affects devices with specific Qualcomm components.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system crash or freeze requiring hard reboot, potentially causing service disruption in critical systems.

🟠

Likely Case

System instability, application crashes, or degraded performance due to SMMU resource exhaustion.

🟢

If Mitigated

Minimal impact with proper access controls and monitoring in place.

🌐 Internet-Facing: LOW - Requires local access or compromised application to trigger.
🏢 Internal Only: MEDIUM - Malicious insiders or compromised internal applications could exploit this.

🎯 Exploit Status

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

Exploitation requires ability to trigger SMMU register access through driver or application.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Refer to Qualcomm security bulletin for specific firmware/software updates.

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

Restart Required: Yes

Instructions:

1. Check Qualcomm advisory for affected chipset list. 2. Obtain firmware/software updates from device manufacturer. 3. Apply updates following manufacturer instructions. 4. Reboot device.

🔧 Temporary Workarounds

Restrict SMMU access

Linux-based systems

Limit which applications/drivers can access SMMU global registers through system permissions.

Specific commands depend on OS and configuration; implement via SELinux/AppArmor policies or system permissions.

🧯 If You Can't Patch

  • Implement strict application sandboxing to limit SMMU access.
  • Monitor system logs for unusual SMMU-related activity or resource exhaustion patterns.

🔍 How to Verify

Check if Vulnerable:

Check device chipset against Qualcomm advisory list; examine system logs for SMMU-related errors.

Check Version:

Device-specific; typically 'cat /proc/cpuinfo' or manufacturer-specific commands for chipset/firmware version.

Verify Fix Applied:

Verify firmware/software version matches patched version from manufacturer; monitor for SMMU stability.

📡 Detection & Monitoring

Log Indicators:

  • Kernel logs showing SMMU errors, resource exhaustion warnings, or system instability events.

Network Indicators:

  • None - this is a local hardware/firmware vulnerability.

SIEM Query:

Search for 'SMMU', 'resource exhaustion', or system crash events in kernel/system logs.

🔗 References

📤 Share & Export