CVE-2024-45584
📋 TL;DR
This vulnerability allows memory corruption when userspace makes a compat IOCTL call followed by a normal IOCTL call, potentially leading to privilege escalation or denial of service. It affects Qualcomm-based devices and systems using vulnerable Qualcomm components. Attackers could exploit this to gain elevated privileges or crash systems.
💻 Affected Systems
- Qualcomm chipsets and components
📦 What is this software?
Snapdragon 4 Gen 1 Mobile Firmware by Qualcomm
View all CVEs affecting Snapdragon 4 Gen 1 Mobile Firmware →
Snapdragon 480 5g Mobile Firmware by Qualcomm
Snapdragon 480 5g Mobile Firmware by Qualcomm
Snapdragon 680 4g Mobile Firmware by Qualcomm
Snapdragon 685 4g Mobile Firmware by Qualcomm
Snapdragon 695 5g Mobile Firmware by Qualcomm
Snapdragon 8 Gen 2 Mobile Firmware by Qualcomm
View all CVEs affecting Snapdragon 8 Gen 2 Mobile Firmware →
Snapdragon 8 Gen 2 Mobile Firmware by Qualcomm
View all CVEs affecting Snapdragon 8 Gen 2 Mobile Firmware →
Snapdragon 8 Gen 3 Mobile Firmware by Qualcomm
View all CVEs affecting Snapdragon 8 Gen 3 Mobile Firmware →
Snapdragon Auto 5g Modem Rf Gen 2 Firmware by Qualcomm
View all CVEs affecting Snapdragon Auto 5g Modem Rf Gen 2 Firmware →
Snapdragon W5\+ Gen 1 Wearable Firmware by Qualcomm
View all CVEs affecting Snapdragon W5\+ Gen 1 Wearable Firmware →
Snapdragon X35 5g Modem Rf Firmware by Qualcomm
View all CVEs affecting Snapdragon X35 5g Modem Rf Firmware →
Snapdragon X72 5g Modem Rf Firmware by Qualcomm
View all CVEs affecting Snapdragon X72 5g Modem Rf Firmware →
Snapdragon X75 5g Modem Rf Firmware by Qualcomm
View all CVEs affecting Snapdragon X75 5g Modem Rf Firmware →
Video Collaboration Vc1 Platform Firmware by Qualcomm
View all CVEs affecting Video Collaboration Vc1 Platform Firmware →
Video Collaboration Vc5 Platform Firmware by Qualcomm
View all CVEs affecting Video Collaboration Vc5 Platform Firmware →
Vision Intelligence 400 Firmware by Qualcomm
⚠️ Risk & Real-World Impact
Worst Case
Full system compromise with kernel-level code execution, allowing attackers to bypass security controls, install persistent malware, or access sensitive data.
Likely Case
Local privilege escalation allowing unprivileged users to gain root/admin access, or denial of service causing system instability or crashes.
If Mitigated
Limited impact with proper access controls and isolation, potentially only affecting specific services or containers.
🎯 Exploit Status
Requires local access and ability to make specific IOCTL calls; exploitation depends on memory layout and timing.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Patches available per Qualcomm February 2025 security bulletin
Vendor Advisory: https://docs.qualcomm.com/product/publicresources/securitybulletin/february-2025-bulletin.html
Restart Required: No
Instructions:
1. Check Qualcomm advisory for specific patches for your chipset. 2. Apply vendor-provided patches or firmware updates. 3. Update affected drivers/kernel modules. 4. Verify patch application through version checks.
🔧 Temporary Workarounds
Restrict IOCTL access
allLimit userspace access to vulnerable IOCTL interfaces through SELinux/apparmor policies or capability restrictions
setcap -r /path/to/vulnerable_binary
chmod 750 /dev/vulnerable_device
🧯 If You Can't Patch
- Implement strict access controls to limit which users can execute vulnerable IOCTL calls
- Isolate affected systems in network segments and monitor for suspicious activity
🔍 How to Verify
Check if Vulnerable:
Check Qualcomm chipset/driver versions against affected versions in February 2025 bulletin; examine kernel logs for IOCTL-related warnings
Check Version:
uname -r && modinfo qualcomm_driver_module | grep version
Verify Fix Applied:
Verify patch application through driver/kernel version checks; test IOCTL functionality remains operational without crashes
📡 Detection & Monitoring
Log Indicators:
- Kernel logs showing memory corruption warnings
- IOCTL-related errors or crashes in system logs
- Unexpected privilege escalation attempts
Network Indicators:
- None - local exploitation only
SIEM Query:
source="kernel" AND ("corruption" OR "IOCTL" OR "segfault") AND process="vulnerable_driver"