CVE-2024-49845

7.8 HIGH

📋 TL;DR

This vulnerability involves memory corruption during the FRS UDS generation process in Qualcomm components, potentially allowing attackers to execute arbitrary code or cause denial of service. It affects devices using vulnerable Qualcomm chipsets, primarily mobile devices and IoT products.

💻 Affected Systems

Products:
  • Qualcomm chipsets with FRS UDS functionality
Versions: Specific versions not detailed in reference; check Qualcomm advisory for affected chipset models
Operating Systems: Android, Linux-based systems using Qualcomm components
Default Config Vulnerable: ⚠️ Yes
Notes: Affects devices with vulnerable Qualcomm firmware; exact models depend on chipset implementation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

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

🟠

Likely Case

Local privilege escalation or denial of service affecting device stability and availability.

🟢

If Mitigated

Limited impact with proper memory protections and exploit mitigations in place.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: HIGH

🎯 Exploit Status

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

Exploitation likely requires local access or specific conditions; memory corruption vulnerabilities can be leveraged for privilege escalation.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Refer to Qualcomm security bulletin for specific firmware versions

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

Restart Required: Yes

Instructions:

1. Check Qualcomm advisory for affected chipset models. 2. Obtain updated firmware from device manufacturer. 3. Apply firmware update following manufacturer instructions. 4. Reboot device to activate patch.

🔧 Temporary Workarounds

Restrict local access

all

Limit physical and network access to vulnerable devices to reduce attack surface.

🧯 If You Can't Patch

  • Isolate affected devices on segmented networks with strict access controls.
  • Implement application allowlisting and memory protection mechanisms where supported.

🔍 How to Verify

Check if Vulnerable:

Check device chipset model and firmware version against Qualcomm advisory; use 'cat /proc/cpuinfo' on Linux systems to identify Qualcomm chips.

Check Version:

Check manufacturer-specific commands for firmware version (e.g., 'getprop ro.build.version.incremental' on Android).

Verify Fix Applied:

Verify firmware version has been updated to patched release specified in Qualcomm bulletin.

📡 Detection & Monitoring

Log Indicators:

  • Kernel panic logs, memory corruption errors in system logs, unexpected process crashes

Network Indicators:

  • Unusual local network traffic to/from affected devices

SIEM Query:

Search for events related to kernel crashes or privilege escalation attempts on devices with Qualcomm chipsets.

🔗 References

📤 Share & Export