CVE DatabaseCVE-2020-11261
한국어 권고문 →
CVE-2020-112617.8/HIGHCISA KEVCWE-787CWE-20

Qualcomm Snapdragon Chipset Memory Corruption and Local Privilege Escalation Vulnerability (CVE-2020-11261) Analysis & Mitigation Guide

⚡ Jump to Patch
Affected Vendors
qualcomm
Affected Components
snapdragon auto, snapdragon compute, snapdragon connectivity, snapdragon consumer iot, snapdragon industrial iot, snapdragon mobile, snapdragon voice & music, snapdragon wearables
Published Date
2021-06-09
CVSS v3.1
7.8
HIGH
EPSS (30d)
1.5%
FIRST.org
CISA KEV
Exploited

Executive & SecOps Summary

SECOPS ASSESSMENT
Affected Scope

Android and embedded devices powered by Snapdragon Auto, Compute, Connectivity, Consumer IoT, Industrial IoT, Mobile, Voice & Music, and Wearables chipsets

Impact

Local attackers can trigger memory corruption (CWE-787) due to improper input validation when requesting huge memory allocations, potentially leading to local privilege escalation (LPE) and arbitrary code execution

Mitigation

Apply the latest security patches released by device OEMs (January 2021 or later) and update Android devices to the latest security patch level

Affected Products & Version Scope

All devices utilizing Qualcomm Snapdragon Auto, Compute, Connectivity, Consumer IoT, Industrial IoT, Mobile, Voice & Music, and Wearables chipsets without the January 2021 security patch applied

Remediation & Live Workaround Commands

PATCH & WORKAROUND

1. Official Patch & Version Upgrade Commands

For Android and embedded devices, apply the firmware updates provided by your device OEM corresponding to Qualcomm's January 2021 Security Bulletin. Verify the current security patch level of your Android device using the following commands:

bash
# Check Android security patch level via ADB (Requires 2021-01-05 or later)
adb shell getprop ro.build.version.security_patch

# Check system build ID and kernel version
adb shell getprop ro.build.display.id
adb shell uname -r

2. Temporary Workaround & Hardening Configuration

For legacy or embedded devices where firmware updates are not immediately feasible, restrict local access and disable untrusted application execution. Disable ADB debugging and restrict shell access.

bash
# Disable ADB debugging on the device to prevent local shell access
adb shell settings put global adb_enabled 0

# Verify SEAndroid (SELinux) is in Enforcing mode to mitigate privilege escalation
adb shell getenforce
# Force Enforcing mode if it is set to Permissive (requires root)
adb shell setenforce 1

3. Log Audit & IoC Verification Commands

Monitor system logs (dmesg or logcat) for abnormal memory allocation failures or kernel panics related to kgsl or ion drivers.

bash
# Scan logcat for memory corruption or driver allocation failures
adb logcat -d | grep -Ei 'kgsl|ion|out of memory|segfault|memory corruption'

# Monitor kernel dmesg logs for driver allocation errors in real-time
adb shell dmesg | grep -E -i 'alloc|fail|invalid'
Interactive SecOps Remediation Checklist
0/4 (0%)
Recommended Security Control & Mitigation Partner
SentinelOne Singularity AI EDR
Due to active exploitation in the wild, immediately update all Android and Snapdragon-based embedded devices to the January 2021 security patch level or later.

Block Kernel Privilege Escalation & Ransomware Payloads Before You Can Reboot

Protect unpatched Windows, Linux, and macOS workloads against in-memory exploitation and lateral movement with autonomous EDR.

100% MITRE ATT&CK Detection · 1-Click Rollback

Technical Root Cause & Exploitation Mechanics

1. Vulnerability Overview & Root Cause

This vulnerability (CVE-2020-11261) is a critical memory corruption issue residing in the memory management component of Qualcomm Snapdragon chipsets. When a user-space application requests a memory allocation of an exceptionally huge size, the system fails to properly validate the input and return an error (CWE-20). This lack of validation leads to an integer overflow or out-of-bounds write (CWE-787) during the physical memory mapping process, corrupting critical system memory regions.

2. Exploitation Mechanics & Attack Scenario

An attacker with local access and low privileges (PR:L) on the target device can exploit this vulnerability. The typical attack scenario proceeds as follows:

  • The attacker sends a crafted memory allocation request with an extremely large size parameter (e.g., close to 0xFFFFFFFF) to the Qualcomm shared memory driver (such as kgsl or ion).
  • Due to improper validation, the driver bypasses error handling and attempts to allocate the memory, resulting in an integer wrap-around that allocates a very small buffer instead.
  • Subsequent write or copy operations into this buffer exceed its actual boundaries, causing an Out-of-Bounds Write (CWE-787) into adjacent kernel memory.
  • By corrupting kernel structures (such as process credentials), the attacker escalates privileges to root.

3. Infrastructure & Business Impact

As this vulnerability is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, active exploitation in the wild has been confirmed. Because it affects a vast range of Snapdragon chipsets across mobile, automotive, industrial IoT, and wearables, successful exploitation can lead to complete device takeover, sensitive data exfiltration, and operational disruption in enterprise BYOD environments, smart factories, and connected vehicle infrastructures.

Official Vendor Advisories & References

NVD Original English Description

Memory corruption due to improper check to return error when user application requests memory allocation of a huge size in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

Frequently Asked SecOps Questions (CVE-2020-11261)

FAQ

Q1. How critical is CVE-2020-11261 and is it actively exploited in the wild?

CVE-2020-11261 is rated CVSS 7.8 (HIGH) with a 30-day EPSS exploitation probability of 1.5%. It is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, requiring immediate emergency remediation.

Q2. Which vendors and products are affected by CVE-2020-11261?

Primary impacted vendors include qualcomm across snapdragon auto, snapdragon compute, snapdragon connectivity, snapdragon consumer iot, snapdragon industrial iot, snapdragon mobile, snapdragon voice & music, snapdragon wearables. Scope summary: All devices utilizing Qualcomm Snapdragon Auto, Compute, Connectivity, Consumer IoT, Industrial IoT, Mobile, Voice & Music, and Wearables chipsets without the January 2021 security patch applied

Q3. What temporary mitigations or workarounds exist for CVE-2020-11261 before patching?

[Mitigation] Apply the latest security patches released by device OEMs (January 2021 or later) and update Android devices to the latest security patch level Follow the CLI remediation commands and interactive SecOps checklist on this page to restrict exposure prior to your maintenance window.

SECOPS WORKBENCH INTEGRATION

Generate an Internal Engineering Notice or CISO Report for CVE-2020-11261

Instantly format this advisory into an executive CISO summary or engineering patch ticket.

Generate Report →

🔗 Related Advisories in Similar Stack (qualcomm)

View Category →
SecOps Advisory Dispatch & RSS Feed

Subscribe to Daily Vulnerability Briefings & KEV Alerts

Concise morning briefings for SecOps, DevSecOps, and SRE teams covering newly exploited CVEs and mitigation priorities.

Slack / Teams / RSS Feed:
PatchKO
CVE-2020-11261 Qualcomm Snapdragon Chipset Memory Corruption and Local Privilege Escalation Vulnerability (CVE-2020-11261) Analysis & Mitigation Guide (CVSS 7.8) - Patch & Workaround | CVE Pulse