CVE-2025-47325

6.5 MEDIUM

📋 TL;DR

This vulnerability allows attackers to access sensitive information by exploiting improper handling of system calls with invalid parameters. It affects systems using Qualcomm chipsets with vulnerable firmware. The information disclosure could reveal kernel memory contents or other protected data.

💻 Affected Systems

Products:
  • Qualcomm chipsets and devices using vulnerable firmware
Versions: Specific versions listed in Qualcomm December 2025 security bulletin
Operating Systems: Android, Linux-based systems using Qualcomm chipsets
Default Config Vulnerable: ⚠️ Yes
Notes: Affects devices with specific Qualcomm chipset firmware versions. Check Qualcomm advisory for exact models.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could read kernel memory, potentially exposing encryption keys, passwords, or other sensitive system data leading to full system compromise.

🟠

Likely Case

Limited information disclosure revealing system state or configuration details that could aid further attacks.

🟢

If Mitigated

Minimal impact with proper access controls and network segmentation limiting exposure.

🌐 Internet-Facing: MEDIUM - Requires system call access which typically needs local or network access, but could be combined with other vulnerabilities.
🏢 Internal Only: HIGH - Local attackers or compromised applications could exploit this to escalate privileges or gather sensitive information.

🎯 Exploit Status

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

Requires ability to make system calls with invalid parameters, typically through local access or compromised applications.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Firmware versions specified in December 2025 Qualcomm security bulletin

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

Restart Required: Yes

Instructions:

1. Check Qualcomm advisory for affected chipset models. 2. Contact device manufacturer for firmware updates. 3. Apply firmware patches provided by device vendor. 4. Reboot device after update.

🔧 Temporary Workarounds

Restrict system call access

linux

Implement seccomp filters or similar mechanisms to restrict which system calls applications can make

Implement via application sandboxing or container security policies

Application sandboxing

linux

Run potentially untrusted applications in restricted environments with limited system call access

Use SELinux/AppArmor policies to restrict application capabilities

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate vulnerable devices
  • Monitor for unusual system call patterns and privilege escalation attempts

🔍 How to Verify

Check if Vulnerable:

Check device firmware version against Qualcomm advisory list of vulnerable versions

Check Version:

cat /proc/version or check device firmware settings

Verify Fix Applied:

Verify firmware version matches or exceeds patched versions listed in Qualcomm bulletin

📡 Detection & Monitoring

Log Indicators:

  • Failed system calls with unusual parameters
  • Kernel panic or warning messages related to system call handling

Network Indicators:

  • Unusual local process communication patterns

SIEM Query:

Search for kernel logs containing 'invalid parameter' or 'system call error' from Qualcomm-related processes

🔗 References

📤 Share & Export