# CVE-2021-30309: Memory corruption in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile

> Improper size validation in QXDM commands allows memory corruption, potentially enabling code execution or privilege escalation on Snapdragon devices.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-cwg8-4j87-pp8g

## What is CVE-2021-30309?

CVE-2021-30309 is a high-severity memory corruption vulnerability in Qualcomm Mdm9650 Firmware, published on 11 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper size validation of QXDM commands can lead to memory corruption in Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2021-30309?

It affects 43 products.


Products: Qualcomm Mdm9650 Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6390 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca9377 Firmware, Qualcomm Qcm6125 Firmware, Qualcomm Qcs410 Firmware, Qualcomm Qcs603 Firmware, Qualcomm Qcs605 Firmware, Qualcomm Qcs610 Firmware, Qualcomm Qcs6125 Firmware, Qualcomm Sd660 Firmware, Qualcomm Sd665 Firmware, Qualcomm Sd690 5g Firmware, Qualcomm Sd730 Firmware, Qualcomm Sd765 Firmware, Qualcomm Sd765g Firmware, Qualcomm Sd768g Firmware, Qualcomm Sd865 5g Firmware, Qualcomm Sd870 Firmware and 23 more.

## How do I fix CVE-2021-30309?

No fix has been published for CVE-2021-30309 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-30309 being exploited?

There is no known exploitation of CVE-2021-30309 in the wild and no public exploit code.

## Other vulnerabilities in Qualcomm Mdm9650 Firmware

- [CVE-2019-2252](https://insights.sbomify.com/CVE-2019-2252/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-2256](https://insights.sbomify.com/CVE-2019-2256/): Code injection in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2016-10461](https://insights.sbomify.com/CVE-2016-10461/): Memory corruption in Snapdragon Mobile (critical 9.8)
- [CVE-2017-18135](https://insights.sbomify.com/CVE-2017-18135/): Memory corruption in Snapdragon Mobile (critical 9.8)
- [CVE-2017-18142](https://insights.sbomify.com/CVE-2017-18142/): Memory corruption in Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-30309 and fix it if it is affected.

What it is: CVE-2021-30309 is a high-severity memory corruption vulnerability in Qualcomm Mdm9650 Firmware, published on 11 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-30309 in the wild and no public exploit code.

Affected product: Qualcomm Mdm9650 Firmware. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-30309/ (Markdown: https://insights.sbomify.com/CVE-2021-30309/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-30309
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-30309
- OSV: https://osv.dev/vulnerability/CVE-2021-30309

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-30309/
Summaries are generated and may contain mistakes; the official description above is the record.