CVE-2024-45547

7.8 HIGH

📋 TL;DR

This vulnerability allows memory corruption through a specific IOCTL call when processing FIPS encryption/decryption verification in Qualcomm components. Attackers could potentially execute arbitrary code or cause system crashes. Affects devices with Qualcomm chipsets that implement the vulnerable FIPS functionality.

💻 Affected Systems

Products:
  • Qualcomm chipsets with FIPS encryption/decryption functionality
Versions: Specific versions not detailed in reference; check Qualcomm advisory for exact affected versions
Operating Systems: Android, Linux, and other OS using Qualcomm components
Default Config Vulnerable: ⚠️ Yes
Notes: Requires user-space access to invoke the vulnerable IOCTL call

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

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

🟠

Likely Case

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

🟢

If Mitigated

System crash or denial of service if memory corruption cannot be leveraged for code execution.

🌐 Internet-Facing: LOW (requires local access or specific conditions for remote exploitation)
🏢 Internal Only: MEDIUM (local attackers could exploit for privilege escalation)

🎯 Exploit Status

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

Requires local access and knowledge of the specific IOCTL interface; memory corruption exploitation requires additional techniques

🛠️ 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: No

Instructions:

1. Check Qualcomm advisory for affected chipset versions. 2. Obtain firmware/software updates from device manufacturer. 3. Apply patches according to manufacturer instructions. 4. Verify patch installation.

🔧 Temporary Workarounds

Restrict IOCTL access

Linux-based systems

Limit user-space access to the vulnerable IOCTL interface through SELinux/AppArmor policies or kernel module restrictions

# Example: Add SELinux policy to restrict ioctl access
# consult your specific OS documentation for exact commands

🧯 If You Can't Patch

  • Implement strict access controls to prevent untrusted users from accessing the vulnerable interface
  • Monitor for abnormal IOCTL calls and system crashes related to FIPS functionality

🔍 How to Verify

Check if Vulnerable:

Check Qualcomm chipset version and compare against advisory; examine system logs for FIPS-related IOCTL calls

Check Version:

# Check Qualcomm chipset version: cat /proc/cpuinfo | grep -i qualcomm

Verify Fix Applied:

Verify patch version from Qualcomm bulletin is installed; test FIPS functionality after patching

📡 Detection & Monitoring

Log Indicators:

  • Kernel panic logs
  • IOCTL access violations
  • FIPS module crash reports

Network Indicators:

  • Not network exploitable; focus on local system monitoring

SIEM Query:

source="kernel" AND ("panic" OR "ioctl" OR "FIPS")

🔗 References

📤 Share & Export