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-49837 Overview
CVE-2024-49837 is a memory corruption vulnerability in multiple Qualcomm automotive and connectivity firmware components. The flaw occurs while reading CPU state data during a guest virtual machine (VM) suspend operation. The root cause is categorized as improper validation of array index [CWE-129], which allows an attacker with local, low-privileged access to trigger memory corruption in the hypervisor context.
Qualcomm addressed the issue in the Qualcomm February 2025 Security Bulletin. The vulnerability affects a broad range of Snapdragon automotive platforms and QCA connectivity chipsets used in telematics, infotainment, and advanced driver-assistance systems.
Critical Impact
Successful exploitation can corrupt hypervisor memory during guest VM suspend, enabling privilege escalation from a guest context to compromise host confidentiality, integrity, and availability.
Affected Products
- Qualcomm Snapdragon Auto platforms (SA8255P, SA8295P, SA8540P, SA8620P, SA8650P, SA8770P, SA8775P, SA9000P, SA7255P, SA7775P)
- Qualcomm QAM-series automotive modules (QAM8255P, QAM8295P, QAM8620P, QAM8650P, QAM8775P, QAMSRV1H, QAMSRV1M)
- Qualcomm QCA connectivity chipsets (QCA6574AU, QCA6595, QCA6595AU, QCA6688AQ, QCA6696, QCA6698AQ) and SRV1H/SRV1L/SRV1M platforms
Discovery Timeline
- 2025-02-03 - CVE-2024-49837 published to NVD alongside the Qualcomm February 2025 Security Bulletin
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-49837
Vulnerability Analysis
The vulnerability resides in the hypervisor code path that reads CPU state data when a guest VM transitions into a suspend state. During this operation, the firmware consumes an index or offset derived from guest-controlled context without sufficient bounds validation. The resulting out-of-bounds memory access corrupts hypervisor data structures.
Because the affected code executes with hypervisor privileges on Qualcomm automotive SoCs, memory corruption at this layer can cross the guest-to-host trust boundary. Attackers who already hold local, low-privileged execution inside a guest VM can leverage the flaw to influence host-side memory, undermining the virtualization isolation model used across infotainment, telematics, and vehicle-safety domains.
Root Cause
The weakness is classified as Improper Validation of Array Index [CWE-129]. The hypervisor accepts an index value used to retrieve CPU state information during VM suspend without confirming that it falls within the bounds of the backing buffer. When the index exceeds expected limits, the resulting read or subsequent write operation corrupts adjacent memory structures used by the hypervisor to track guest state.
Attack Vector
Exploitation requires local access with low privileges on the affected device and does not require user interaction. An attacker with code execution inside a guest VM triggers a suspend operation while supplying a crafted state that influences the vulnerable index. The hypervisor then performs the out-of-bounds access, corrupting memory in a controlled fashion. See the Qualcomm February 2025 Security Bulletin for the authoritative technical description.
Detection Methods for CVE-2024-49837
Indicators of Compromise
- Unexpected guest VM suspend or resume failures logged by the hypervisor on affected Snapdragon Auto or QCA platforms
- Kernel or hypervisor crash dumps referencing CPU state read paths during VM lifecycle transitions
- Repeated abnormal reboots of telematics, infotainment, or ADAS subsystems following guest workload activity
Detection Strategies
- Inventory vehicle and embedded assets against the affected Qualcomm part numbers listed in the February 2025 bulletin and verify firmware build identifiers
- Monitor OEM-provided telemetry for hypervisor fault signatures tied to VM suspend operations
- Correlate guest VM crash events with host-side anomalies to identify potential cross-boundary memory corruption attempts
Monitoring Recommendations
- Enable and centrally collect hypervisor and secure-world diagnostic logs from affected automotive ECUs where OEM tooling permits
- Baseline normal VM suspend and resume frequency, and alert on statistically anomalous bursts originating from a single guest
- Track firmware version drift across fleets to confirm that patched builds are deployed and remain in place after OTA updates
How to Mitigate CVE-2024-49837
Immediate Actions Required
- Identify all deployed hardware matching the affected Qualcomm chipsets and firmware components
- Apply the firmware updates referenced in the Qualcomm February 2025 Security Bulletin through the device OEM or Tier 1 supplier
- Restrict and audit which workloads are permitted to run inside guest VMs on affected hypervisors, prioritizing systems that execute third-party or untrusted code
Patch Information
Qualcomm published fixes for CVE-2024-49837 in the February 2025 Security Bulletin. Patches are distributed to downstream OEMs, who integrate them into vehicle and device firmware releases. Operators should coordinate with their hardware vendors to confirm the exact patched firmware build for each affected platform.
Workarounds
- No vendor-supplied workaround is published; firmware updates from the February 2025 bulletin are the required remediation
- Where patch deployment is delayed, limit local access to affected systems and reduce the attack surface available to guest workloads
- Enforce code-signing and secure boot policies on guest VM images to raise the barrier for an attacker gaining the local foothold needed to trigger the flaw
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

