# CVE-2021-30259: Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking

> Out-of-bounds access in Qualcomm Snapdragon firmware allows attackers to execute arbitrary code or cause denial of service.

- **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:** 12 Nov 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-rhjm-5wg5-jr2x

## What is CVE-2021-30259?

CVE-2021-30259 is a high-severity memory corruption vulnerability in Qualcomm Aqt1000 Firmware, published on 12 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Possible out of bound access due to improper validation of function table entries in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 158 products.


Products: Qualcomm Aqt1000 Firmware, Qualcomm Ar8031 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Csrb31024 Firmware, Qualcomm Mdm9150 Firmware, Qualcomm Mdm9205 Firmware, Qualcomm Mdm9250 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Mdm9655 Firmware, Qualcomm Qca4004 Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6175a Firmware, Qualcomm Qca6310 Firmware, Qualcomm Qca6320 Firmware, Qualcomm Qca6335 Firmware, Qualcomm Qca6390 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6420 Firmware and 138 more.

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

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

## Is CVE-2021-30259 being exploited?

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

## Other vulnerabilities in Qualcomm Aqt1000 Firmware

- [CVE-2025-21479](https://insights.sbomify.com/CVE-2025-21479/): Qualcomm Multiple Chipsets Incorrect Authorization (high 8.6, exploited in the wild)
- [CVE-2025-21480](https://insights.sbomify.com/CVE-2025-21480/): Qualcomm Multiple Chipsets Incorrect Authorization (high 8.6, exploited in the wild)
- [CVE-2023-28562](https://insights.sbomify.com/CVE-2023-28562/): Buffer Copy Without Checking Size of Input in QESL (critical 9.8)
- [CVE-2022-40514](https://insights.sbomify.com/CVE-2022-40514/): Buffer copy without checking size of input in WLAN Firmware (critical 9.8)
- [CVE-2022-22096](https://insights.sbomify.com/CVE-2022-22096/): Memory corruption in Snapdragon Connectivity, Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-30259 is a high-severity memory corruption vulnerability in Qualcomm Aqt1000 Firmware, published on 12 Nov 2021. 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-30259 in the wild and no public exploit code.

Affected product: Qualcomm Aqt1000 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-30259/ (Markdown: https://insights.sbomify.com/CVE-2021-30259/index.md)
```

## Sources

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

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