CVE-2024-38402
📋 TL;DR
This vulnerability allows attackers to cause memory corruption through a specific IOCTL call for group information retrieval. Successful exploitation could lead to arbitrary code execution or system crashes. Affects systems using vulnerable Qualcomm components, particularly mobile devices and embedded 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 4 Gen 2 Mobile Firmware by Qualcomm
View all CVEs affecting Snapdragon 4 Gen 2 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 778g 5g Mobile Firmware by Qualcomm
View all CVEs affecting Snapdragon 778g 5g Mobile Firmware →
Snapdragon 778g 5g Mobile Firmware by Qualcomm
View all CVEs affecting Snapdragon 778g 5g Mobile Firmware →
Snapdragon 780g 5g Mobile Firmware by Qualcomm
View all CVEs affecting Snapdragon 780g 5g Mobile Firmware →
Snapdragon 782g Mobile Firmware by Qualcomm
Snapdragon 7c\+ Gen 3 Compute Firmware by Qualcomm
View all CVEs affecting Snapdragon 7c\+ Gen 3 Compute Firmware →
Snapdragon 8 Gen 1 Mobile Firmware by Qualcomm
View all CVEs affecting Snapdragon 8 Gen 1 Mobile Firmware →
Snapdragon 8 Gen 1 Mobile Firmware by Qualcomm
View all CVEs affecting Snapdragon 8 Gen 1 Mobile Firmware →
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 888 5g Mobile Firmware by Qualcomm
Snapdragon 888 5g Mobile Firmware by Qualcomm
Snapdragon Auto 5g Modem Rf Firmware by Qualcomm
View all CVEs affecting Snapdragon Auto 5g Modem Rf 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 X62 5g Modem Rf Firmware by Qualcomm
View all CVEs affecting Snapdragon X62 5g Modem Rf Firmware →
Snapdragon X65 5g Modem Rf Firmware by Qualcomm
View all CVEs affecting Snapdragon X65 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 Vc3 Platform Firmware by Qualcomm
View all CVEs affecting Video Collaboration Vc3 Platform Firmware →
⚠️ Risk & Real-World Impact
Worst Case
Full system compromise with kernel-level privileges leading to complete device control, data theft, or persistent backdoor installation.
Likely Case
Local privilege escalation allowing attackers to gain elevated permissions on already compromised devices.
If Mitigated
System crash or denial of service if memory corruption cannot be reliably controlled for code execution.
🎯 Exploit Status
Requires local access and ability to make IOCTL calls. Memory corruption vulnerabilities can be challenging to weaponize reliably.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Refer to Qualcomm September 2024 security bulletin for specific patched versions
Vendor Advisory: https://docs.qualcomm.com/product/publicresources/securitybulletin/september-2024-bulletin.html
Restart Required: Yes
Instructions:
1. Check Qualcomm advisory for affected chipset/component versions. 2. Obtain updated firmware/drivers from device manufacturer. 3. Apply patches following manufacturer's instructions. 4. Reboot device to load patched components.
🔧 Temporary Workarounds
Restrict IOCTL access
linuxLimit access to vulnerable IOCTL interfaces through SELinux/AppArmor policies or kernel module restrictions
# Example SELinux policy to restrict ioctl access
# require device-specific policy configuration
🧯 If You Can't Patch
- Implement strict application sandboxing to limit potential damage from exploitation
- Monitor for unusual IOCTL calls or memory corruption events in system logs
🔍 How to Verify
Check if Vulnerable:
Check device firmware/chipset version against Qualcomm's advisory. Use 'getprop ro.bootloader' or similar on Android devices.
Check Version:
adb shell getprop ro.bootloader (Android) or uname -a (Linux kernel)
Verify Fix Applied:
Verify updated firmware version matches patched versions in Qualcomm bulletin. Check kernel/driver version strings.
📡 Detection & Monitoring
Log Indicators:
- Kernel panic logs
- IOCTL access violations in audit logs
- Memory corruption warnings in dmesg
Network Indicators:
- Not network exploitable - local vulnerability
SIEM Query:
source="kernel" AND ("panic" OR "corruption" OR "ioctl")