dbcve.org
Snapdragon Ar2 Gen 1 FirmwareOperating system · Qualcomm

CVE-2024-49841

HIGH · 7.8 CVSS v3.1 Published 2025-05-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Memory corruption during memory assignment to headless peripheral VM due to incorrect error code handling.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Memory corruption occurs in the hypervisor when assigning memory to headless peripheral virtual machines due to improper handling of error codes returned during memory allocation operations. The incorrect error code handling allows corrupted or uninitialized memory to be used, potentially leading to VM escape or data integrity issues.

MitigationFix the error code handling paths in the memory assignment logic for headless peripheral VMs to ensure proper validation and error propagation. Implement bounds checking and memory initialization before use.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Snapdragon Ar2 Gen 1 FirmwareOperating system
Affected:all versions
Snapdragon Auto 5g Modem Rf Gen 2 FirmwareOperating system
Affected:all versions
Snapdragon X24 Lte Modem FirmwareOperating system
Affected:all versions
Snapdragon X32 5g Modem Rf FirmwareOperating system
Affected:all versions
Snapdragon X35 5g Modem Rf FirmwareOperating system
Affected:all versions
Snapdragon X50 5g Modem Rf FirmwareOperating system
Affected:all versions
Snapdragon X55 5g Modem Rf FirmwareOperating system
Affected:all versions
Snapdragon X62 5g Modem Rf System FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the exact firmware version installed on the Qualcomm modem or system-on-chip
    Access the modem firmware information via AT commands (such as AT+CGMR or AT+GMR), vendor diagnostic tools, or system logs. On Android devices, check /proc/bootinfo, /sys/firmware/devicetree, or use 'getprop' for radio firmware versions.
    Affected if The installed firmware version matches one of the affected product names listed in the CVE and the vendor has not issued a patch for this specific CVE.
  2. Determine if the hypervisor feature is enabled on the device
    Examine the hypervisor configuration or boot parameters. Check system configuration files related to virtualization or trust zone settings. Look for hypervisor-related kernel parameters or boot loader configurations.
    Affected if The hypervisor is active and the device uses headless peripheral virtual machines that perform memory allocation operations.
  3. Check for memory assignment operations to headless peripheral VMs
    Review system logs, hypervisor debug logs, or memory allocation traces for any errors or warnings related to VM memory assignment. Inspect any available diagnostic interfaces that expose hypervisor memory management behavior.
    Affected if Logs or diagnostics show error code handling issues during VM memory allocation, or memory corruption events involving peripheral VMs.
  4. Verify if the device configuration uses headless peripheral VMs
    Examine the hypervisor or virtualization configuration to determine if headless peripheral VMs are instantiated. This may be found in firmware configuration files, device tree bindings, or vendor-specific management interfaces.
    Affected if The system configures or allows headless peripheral VMs that perform their own memory allocation requests to the hypervisor.

The environment is likely affected if the device runs any of the listed Qualcomm Snapdragon firmware variants (Ar2 Gen 1, Auto 5g Modem Rf Gen 2, X24 LTE, X32 5g, X35 5g, X50 5g, X55 5g, or X62 5g) with the hypervisor and headless peripheral VM features enabled, and the vendor has not confirmed a patch for CVE-2024-49841.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Fix the error code handling paths in the memory assignment logic for headless peripheral VMs to ensure proper validation and error propagation. Implement bounds checking and memory initialization before use.

Fix this in Snapdragon Ar2 Gen 1 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-49841 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-49841 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data