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-33045 Overview
CVE-2024-33045 is a memory corruption vulnerability affecting a broad range of Qualcomm chipsets and firmware. The flaw occurs when the Bluetooth-FM (BTFM) client sends new messages over the Serial Low-power Inter-chip Media Bus (Slimbus) to the Audio Digital Signal Processor (ADSP). An authenticated local attacker with low privileges can trigger the condition to corrupt memory on the device. The vulnerability is tracked under [CWE-787] (Out-of-Bounds Write) and [CWE-562] (Return of Stack Variable Address). Qualcomm addressed the issue in its September 2024 security bulletin.
Critical Impact
Successful exploitation can lead to high-impact compromise of confidentiality, integrity, and availability on affected Snapdragon, FastConnect, and QCA-series platforms, including mobile, automotive, compute, and IoT devices.
Affected Products
- Qualcomm Snapdragon mobile platforms (Snapdragon 8 Gen 1/2/3, 888, 778G, 695 5G, 480 5G, 460, and related series)
- Qualcomm FastConnect connectivity suites (FastConnect 6200, 6700, 6900, 7800) and QCA Wi-Fi/Bluetooth chipsets (QCA6174A, QCA6391, QCA6574, QCA6696, and others)
- Qualcomm automotive, compute, and IoT platforms (SA8155P/SA8255P/SA8295P/SA8775P, QCS/QCM series, Robotics RB5, WCD/WSA/WCN audio and wireless codecs)
Discovery Timeline
- 2024-09-02 - CVE CVE-2024-33045 published to NVD
- September 2024 - Qualcomm releases security patch via Qualcomm September 2024 Security Bulletin
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-33045
Vulnerability Analysis
The flaw lives in the BTFM (Bluetooth-FM) client code path that forwards new messages over Slimbus to the ADSP. Slimbus is a serial interface used to shuttle control and audio data between the application processor and peripheral subsystems. When the BTFM client prepares and dispatches a message, improper handling of message buffers results in memory corruption on the receiving side. The combination of [CWE-787] and [CWE-562] indicates that the code writes outside the bounds of an intended buffer and references stack memory that no longer belongs to the current frame. Exploitation requires local access and low privileges, with no user interaction. Successful corruption can be chained to achieve privileged code execution within the audio subsystem context.
Root Cause
The root cause is unsafe memory handling inside the BTFM-to-ADSP messaging layer. The driver returns or dereferences the address of a stack-allocated variable after its scope has ended ([CWE-562]) and performs a write past the bounds of an allocated buffer ([CWE-787]). Both conditions produce deterministic memory corruption when attacker-controlled message content reaches the vulnerable code path.
Attack Vector
An attacker needs local code execution on the device with low privileges, such as a malicious application granted access to Bluetooth or audio-related interfaces. By issuing crafted BTFM messages that traverse the Slimbus channel to the ADSP, the attacker triggers the out-of-bounds write and stack address misuse. No user interaction is required, and exploitation does not need to cross a trust boundary beyond the local userland.
// No verified public proof-of-concept exists for CVE-2024-33045.
// Refer to the Qualcomm September 2024 Security Bulletin for
// technical remediation details.
Detection Methods for CVE-2024-33045
Indicators of Compromise
- Unexpected ADSP crashes, SubSystem Restart (SSR) events, or kernel panics referencing the BTFM or Slimbus drivers in device logs
- Abnormal Bluetooth or audio service terminations correlated with installation of untrusted applications holding Bluetooth or audio permissions
- Repeated BTFM message errors or Slimbus communication faults recorded in dmesg or vendor diagnostic logs
Detection Strategies
- Monitor Android/embedded device telemetry for abnormal subsystem restarts, especially of the audio DSP, following application installs or Bluetooth session changes
- Review installed applications for unexpected use of Bluetooth, FM, or low-level audio APIs on devices that have not been patched
- Correlate crash dumps and ramdumps with the BTFM/Slimbus call stack to identify likely exploitation attempts
Monitoring Recommendations
- Centralize mobile and IoT device logs to a security data platform for pattern analysis of subsystem crashes and driver faults
- Track Qualcomm firmware and OEM patch levels across the fleet to identify devices still exposed to CVE-2024-33045
- Alert on anomalous Bluetooth stack behavior, including repeated BTFM session establishment failures from a single app
How to Mitigate CVE-2024-33045
Immediate Actions Required
- Apply the firmware updates distributed by Qualcomm and OEMs in response to the Qualcomm September 2024 Security Bulletin
- Inventory all Snapdragon, FastConnect, QCA, WCN, WCD, and WSA components in the fleet and prioritize patching on business-critical and user-exposed devices
- Restrict installation of untrusted applications on affected mobile, automotive, and IoT platforms until updates are deployed
Patch Information
Qualcomm released patches for the affected chipsets in its September 2024 security bulletin. Downstream OEMs (phone, automotive, and IoT vendors) ship these fixes as part of their monthly or quarterly firmware updates. Operators must ensure that both the Qualcomm firmware patch level and the integrating OEM build include the September 2024 (or later) security patch level before considering the device remediated.
Workarounds
- Disable Bluetooth and FM radio functionality on affected devices where operationally feasible until patches are available
- Enforce application allow-listing or mobile device management policies that block untrusted applications from requesting Bluetooth or audio permissions
- Isolate unpatched embedded and automotive devices on segmented networks to limit the reach of a compromised endpoint
# Verify Android security patch level on affected mobile devices
adb shell getprop ro.build.version.security_patch
# Confirm Qualcomm vendor patch level (where exposed)
adb shell getprop ro.vendor.build.security_patch
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

