CVE-2024-45553

7.8 HIGH

📋 TL;DR

This CVE describes a use-after-free vulnerability in Qualcomm components where memory corruption can occur when process-specific maps are improperly handled in global lists. If exploited, it could allow attackers to execute arbitrary code or cause denial of service. This affects devices using vulnerable Qualcomm chipsets and drivers.

💻 Affected Systems

Products:
  • Qualcomm chipsets and associated drivers/firmware
Versions: Specific versions not detailed in reference; check Qualcomm January 2025 bulletin for exact affected versions.
Operating Systems: Android, Linux-based systems using Qualcomm components
Default Config Vulnerable: ⚠️ Yes
Notes: Affects systems with Qualcomm hardware where the vulnerable driver/component is loaded and active.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote code execution with kernel privileges leading to complete system compromise, data theft, or persistent backdoor installation.

🟠

Likely Case

Local privilege escalation allowing attackers to gain elevated permissions on affected devices.

🟢

If Mitigated

Denial of service through system crashes or instability if exploitation attempts are blocked.

🌐 Internet-Facing: MEDIUM - Requires local access or chaining with other vulnerabilities for remote exploitation.
🏢 Internal Only: HIGH - Local attackers or malicious insiders could exploit this for privilege escalation on affected devices.

🎯 Exploit Status

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

Requires local access and timing precision to trigger the race condition between thread operations on global lists.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check Qualcomm January 2025 security bulletin for specific patched versions

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

Restart Required: Yes

Instructions:

1. Check Qualcomm January 2025 security bulletin for your specific chipset/driver. 2. Obtain updated firmware/drivers from device manufacturer or Qualcomm. 3. Apply patches following vendor instructions. 4. Reboot affected devices.

🔧 Temporary Workarounds

Disable vulnerable components

Linux-based systems

If possible, disable or blacklist the specific Qualcomm driver/module containing the vulnerability

modprobe -r [vulnerable_module]
echo 'blacklist [vulnerable_module]' >> /etc/modprobe.d/blacklist.conf

🧯 If You Can't Patch

  • Implement strict access controls to limit local user privileges on affected devices
  • Monitor for unusual process behavior or privilege escalation attempts using security tools

🔍 How to Verify

Check if Vulnerable:

Check Qualcomm chipset/driver version against affected versions in January 2025 bulletin

Check Version:

cat /sys/devices/soc0/*version* or check device firmware information

Verify Fix Applied:

Verify installed Qualcomm driver/firmware version matches patched versions from bulletin

📡 Detection & Monitoring

Log Indicators:

  • Kernel panic logs
  • Driver crash messages
  • Unexpected privilege escalation events

Network Indicators:

  • None - this is a local vulnerability

SIEM Query:

Search for kernel/driver crash events or privilege escalation patterns on devices with Qualcomm hardware

🔗 References

📤 Share & Export