CVE-2024-45584

7.8 HIGH

📋 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

Products:
  • Qualcomm chipsets and components
Versions: Specific versions not detailed in reference; affected versions listed in Qualcomm February 2025 bulletin
Operating Systems: Linux-based systems using Qualcomm drivers
Default Config Vulnerable: ⚠️ Yes
Notes: Affects systems with Qualcomm hardware/drivers; exact configurations depend on specific chipset implementations.

📦 What is this software?

⚠️ 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.

🌐 Internet-Facing: LOW - Requires local access or ability to execute code on the system; not directly exploitable over network.
🏢 Internal Only: MEDIUM - Internal users with local access could exploit for privilege escalation; risk increases in multi-user environments.

🎯 Exploit Status

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

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

all

Limit 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"

🔗 References

📤 Share & Export