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

CVE-2024-33026: Qualcomm AR8035 Firmware DoS Vulnerability

CVE-2024-33026 is a denial of service vulnerability in Qualcomm AR8035 Firmware caused by improper parsing of probe and association response frames. This article covers technical details, affected versions, and mitigation.

Published:

CVE-2024-33026 Overview

CVE-2024-33026 is a transient denial-of-service (DoS) vulnerability affecting a broad range of Qualcomm chipsets and firmware. The flaw resides in the WLAN frame parsing logic for probe response and association response frames. When a received frame length is less than the maximum size of the timestamp field, the parser reads memory out of bounds, causing the WLAN subsystem to crash.

The issue maps to [CWE-126] (Buffer Over-read) and [CWE-125] (Out-of-Bounds Read). It is reachable over the network without authentication or user interaction, impacting hundreds of Qualcomm products including Snapdragon mobile platforms, FastConnect chips, IPQ networking SoCs, and automotive Snapdragon platforms.

Critical Impact

A remote unauthenticated attacker within wireless range can transmit a malformed 802.11 management frame to trigger a transient DoS, disrupting Wi-Fi connectivity on affected Qualcomm devices.

Affected Products

  • Qualcomm Snapdragon 8 Gen 2 / Gen 3 / 8+ Gen 2 Mobile Platforms
  • Qualcomm FastConnect 6700, 6900, and 7800 Wi-Fi chipsets
  • Qualcomm IPQ networking SoCs (IPQ5010 through IPQ9574) and QCA WLAN chips

Discovery Timeline

  • 2024-08-05 - CVE-2024-33026 published to NVD
  • 2024-11-20 - Last updated in NVD database

Technical Details for CVE-2024-33026

Vulnerability Analysis

The vulnerability exists in the Qualcomm WLAN firmware logic that parses IEEE 802.11 probe response and association response management frames. Both frame types include a fixed 8-byte timestamp field at the start of their frame body. The parser assumes the inbound frame contains at least enough bytes to satisfy the maximum timestamp size before reading it.

When an attacker delivers a truncated frame whose total length is smaller than the expected timestamp field size, the parser reads beyond the end of the supplied buffer. This out-of-bounds read corrupts parser state and causes a transient crash of the WLAN subsystem. The DoS condition is non-persistent, but service is interrupted until the WLAN stack recovers.

Root Cause

The root cause is missing length validation before reading the timestamp field from the management frame body. The parsing routine does not verify that the received frame length is greater than or equal to the size of the timestamp before dereferencing it, violating safe parsing practices for untrusted network input.

Attack Vector

Exploitation requires only that the attacker is within radio range of a vulnerable device and is able to transmit raw 802.11 frames. No authentication or association is required, since probe and association responses are processed during the discovery and association phases. An attacker can spoof a malicious access point or inject crafted frames to deliver the truncated payload. The vulnerability affects availability only; it does not provide code execution or information disclosure.

No public proof-of-concept code has been observed in verified repositories. The vulnerability mechanism is described in the Qualcomm August 2024 Security Bulletin.

Detection Methods for CVE-2024-33026

Indicators of Compromise

  • Unexpected, repeated WLAN subsystem crashes or restarts on Qualcomm-based endpoints, IoT, automotive, or networking devices
  • Kernel or HAL logs referencing the WLAN driver fault during probe response or association response processing
  • Repeated client disconnections coinciding with the presence of unknown or rogue access points broadcasting on nearby channels

Detection Strategies

  • Monitor wireless intrusion detection systems (WIDS) for malformed 802.11 management frames with truncated frame bodies below the minimum fixed-field length
  • Correlate device telemetry showing WLAN driver crashes with proximate RF anomalies or rogue SSIDs in the same timeframe
  • Track firmware crash dumps from mobile device management (MDM) platforms for repeated Wi-Fi subsystem faults across multiple endpoints

Monitoring Recommendations

  • Enable centralized logging from MDM, EMM, or endpoint platforms to capture Wi-Fi driver fault events from Qualcomm-based devices
  • Deploy WIDS sensors in high-value environments to alert on anomalous probe response or association response frames
  • Review wireless infrastructure logs for unauthorized SSIDs and unusual client deauthentication patterns that may indicate exploitation attempts

How to Mitigate CVE-2024-33026

Immediate Actions Required

  • Inventory all Qualcomm-based devices listed in the affected products section, including mobile handsets, IoT gateways, automotive head units, and Wi-Fi access points
  • Apply firmware and OEM security updates that incorporate the Qualcomm August 2024 patch level as soon as vendor updates are released
  • Prioritize patching for devices that operate in untrusted RF environments such as public spaces, transit, and shared facilities

Patch Information

Qualcomm released patches as part of the August 2024 security bulletin. Downstream OEMs (Google, Samsung, Xiaomi, automotive manufacturers, and networking vendors) must integrate the fix into their firmware and OS updates. Refer to the Qualcomm August 2024 Security Bulletin for the authoritative list of patched components.

Workarounds

  • Disable Wi-Fi on affected devices when operating in untrusted RF environments until firmware updates are applied
  • Restrict device association to known, trusted SSIDs using MDM policies and enterprise Wi-Fi profile enforcement
  • Deploy enterprise WIDS/WIPS to detect and contain rogue access points that could deliver malformed management frames
bash
# Example: enforce trusted SSID-only policy via MDM (conceptual)
# Restrict Wi-Fi to corporate WPA3-Enterprise SSID and disable auto-join for open networks
mdm policy set wifi.autojoin.open=false
mdm policy set wifi.allowed_ssids="CORP-SECURE"
mdm policy set wifi.disable_in_untrusted_locations=true

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

Default Legacy - Prefooter | Experience the World’s Most Advanced Cybersecurity Platform

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.