CVE-2021-35086

7.5 HIGH

📋 TL;DR

This CVE describes a buffer over-read vulnerability in Qualcomm Snapdragon chipsets when processing NR system information messages. Attackers could potentially read sensitive data from adjacent memory locations. Affected devices include those using Snapdragon Auto, Compute, Connectivity, Industrial IoT, and Mobile platforms.

💻 Affected Systems

Products:
  • Snapdragon Auto
  • Snapdragon Compute
  • Snapdragon Connectivity
  • Snapdragon Industrial IOT
  • Snapdragon Mobile
Versions: Specific chipset versions listed in Qualcomm May 2022 bulletin
Operating Systems: Android, Linux-based automotive/industrial systems
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability exists in baseband/firmware layer, affecting multiple device types including smartphones, automotive systems, and IoT devices

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote code execution leading to complete device compromise, data exfiltration, or persistent backdoor installation

🟠

Likely Case

Information disclosure of adjacent memory contents, potentially exposing sensitive data or system information

🟢

If Mitigated

Limited impact with proper memory protections and exploit mitigations in place

🌐 Internet-Facing: MEDIUM - Requires processing of malicious NR system information messages, which could come from network sources
🏢 Internal Only: MEDIUM - Could be exploited through local network attacks or malicious base stations

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: MEDIUM

Exploitation requires sending specially crafted NR system information messages to vulnerable devices

🛠️ Fix & Mitigation

✅ Official Fix

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

Vendor Advisory: https://www.qualcomm.com/company/product-security/bulletins/may-2022-bulletin

Restart Required: Yes

Instructions:

1. Check device manufacturer for firmware updates. 2. Apply Qualcomm-provided firmware patches. 3. Reboot device after update. 4. Verify patch installation through device settings.

🔧 Temporary Workarounds

Network filtering

all

Implement network filtering to block suspicious NR system information messages

Memory protection

linux

Enable ASLR and other memory protection mechanisms where available

🧯 If You Can't Patch

  • Isolate vulnerable devices from untrusted networks
  • Implement network monitoring for suspicious NR message patterns

🔍 How to Verify

Check if Vulnerable:

Check device chipset model and firmware version against Qualcomm's affected list

Check Version:

Android: 'getprop ro.bootloader' or check Settings > About phone; Linux-based: check manufacturer documentation

Verify Fix Applied:

Verify firmware version has been updated to patched version from manufacturer

📡 Detection & Monitoring

Log Indicators:

  • Baseband/firmware crash logs
  • Memory access violation logs
  • Unexpected system reboots

Network Indicators:

  • Unusual NR system information message patterns
  • Suspicious base station communications

SIEM Query:

Search for baseband/firmware crash events or memory violation alerts in device logs

🔗 References

📤 Share & Export