Skip to main content
Vulnerability Database/CVE-2024-21471

CVE-2024-21471: Qualcomm AR8035 Use-After-Free Vulnerability

CVE-2024-21471 is a use-after-free vulnerability in Qualcomm AR8035 Firmware causing memory corruption during GPU buffer unmapping. This article covers technical details, affected versions, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2024-21471 Overview

CVE-2024-21471 is a memory corruption vulnerability affecting a broad range of Qualcomm Snapdragon chipsets running Linux-based software. The flaw occurs when the Input-Output Memory Management Unit (IOMMU) fails to unmap a Graphics Processing Unit (GPU) buffer, leading to a use-after-free condition [CWE-416]. Qualcomm addressed the issue in its May 2024 Security Bulletin. Because the vulnerability resides in low-level GPU driver code, a local attacker with limited privileges can trigger the condition and corrupt kernel memory on affected devices.

Critical Impact

Successful exploitation can corrupt kernel memory, enabling local privilege escalation and compromise of confidentiality, integrity, and availability on vulnerable Qualcomm-based devices.

Affected Products

  • Qualcomm Snapdragon mobile platforms (including Snapdragon 8 Gen 1/2/3, 888, 865, 845, 835, and others)
  • Qualcomm FastConnect, QCA, WCN, and WCD connectivity and audio firmware families
  • Qualcomm automotive, compute, wearable, XR, and robotics platforms (SA, SG, QCS, QRB, QCM, Snapdragon AR2 Gen 1, Snapdragon W5+ Gen 1)

Discovery Timeline

  • 2024-05-06 - CVE-2024-21471 published to NVD
  • May 2024 - Qualcomm releases security patch via the May 2024 Security Bulletin
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2024-21471

Vulnerability Analysis

The vulnerability is classified as a use-after-free [CWE-416] inside the Qualcomm GPU driver stack on Linux. When a GPU buffer is released, the driver asks the IOMMU to unmap the corresponding Device Virtual Addresses (DVA). If that unmap operation fails, the driver still proceeds to free the backing memory while an active IOMMU mapping or kernel reference may remain. Subsequent GPU DMA activity or kernel operations can then reach freed memory, leading to memory corruption in kernel context. Because GPU buffers are frequently allocated and released by user-space clients, a local attacker with the ability to submit GPU workloads can repeatedly exercise the error path.

Root Cause

The root cause is improper error handling during IOMMU unmap on GPU buffer teardown. The driver does not consistently reconcile the lifecycle of the allocation with the IOMMU state when the unmap call returns an error. This leaves dangling IOMMU translations or stale kernel pointers that reference memory which has been freed and may be reallocated.

Attack Vector

Exploitation requires local access and low privileges, with no user interaction. An attacker running unprivileged code on an affected device can issue crafted sequences of GPU allocation, mapping, and release operations through the exposed GPU ioctl interface. By inducing an IOMMU unmap failure, the attacker triggers the use-after-free and influences the layout of reallocated memory to achieve kernel memory corruption and, ultimately, privilege escalation.

No verified public proof-of-concept is available for CVE-2024-21471. For technical specifics, refer to the Qualcomm May 2024 Security Bulletin.

Detection Methods for CVE-2024-21471

Indicators of Compromise

  • Unexpected kernel crashes, panics, or GPU driver faults referencing IOMMU unmap errors or KGSL/adreno subsystems in dmesg and kernel logs.
  • Repeated allocation and release patterns against GPU device nodes (for example /dev/kgsl-3d0) from unprivileged processes.
  • Processes gaining elevated privileges shortly after heavy GPU ioctl activity.

Detection Strategies

  • Monitor kernel logs for IOMMU unmap failures, SMMU fault messages, and use-after-free indicators associated with GPU buffer teardown.
  • Baseline normal GPU driver interaction and flag unprivileged processes that issue abnormal volumes of GPU memory map/unmap ioctls.
  • Correlate kernel instability events with subsequent credential changes or new privileged process creation on the same device.

Monitoring Recommendations

  • Centralize mobile and embedded device telemetry, including kernel logs and crash reports, into a security data lake for correlation.
  • Track firmware and build fingerprints across the fleet to identify devices still running pre-May 2024 Qualcomm patch levels.
  • Alert on repeated GPU-related kernel faults originating from the same user or application context.

How to Mitigate CVE-2024-21471

Immediate Actions Required

  • Apply the May 2024 (or later) Qualcomm security patch level to all affected devices through the device OEM update channel.
  • Inventory Qualcomm-based endpoints, including automotive, IoT, XR, and wearable platforms, and prioritize patching for devices exposed to untrusted applications.
  • Restrict installation of untrusted applications on affected devices until patches are deployed.

Patch Information

Qualcomm published fixes for CVE-2024-21471 in the Qualcomm May 2024 Security Bulletin. OEMs integrate these patches into their platform security updates. Verify the device security patch level reflects May 2024 or later and that the chipset-specific firmware delivered by the OEM includes the Qualcomm fix.

Workarounds

  • No vendor-supplied workaround is published. Patching remains the only reliable remediation.
  • Reduce exposure by limiting the ability of unprivileged users to install or execute untrusted code that can interact with GPU device nodes.
  • Enforce mobile application vetting and application allow-listing on managed devices pending firmware updates.
bash
# Check Android security patch level on an affected device
adb shell getprop ro.build.version.security_patch
# Expected output should be 2024-05-01 or later for CVE-2024-21471 remediation

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.