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

> Out-of-bounds access in Snapdragon firmware allows attackers to execute code or escalate privileges via improper validation during interface switching.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Jan 2022
- **Updated:** 3 Aug 2024
- **Also known as:** 2873209, A-190408641, GHSA-3xcc-mw3v-cg8g, PUB-A-190408641

## What is CVE-2021-30298?

CVE-2021-30298 is a medium-severity memory corruption vulnerability in Qualcomm Ar8031 Firmware, published on 3 Jan 2022. 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 item size and DIAG memory pools data while switching between USB and PCIE interface in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking

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

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

It affects 61 products.


Products: Qualcomm Ar8031 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Fsm10055 Firmware, Qualcomm Fsm10056 Firmware, Qualcomm Ipq8072a Firmware, Qualcomm Ipq8074a Firmware, Qualcomm Ipq8076a Firmware, Qualcomm Mdm9150 Firmware, Qualcomm Qca6390 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qca6595au Firmware, Qualcomm Qca6696 Firmware, Qualcomm Qca8337 Firmware, Qualcomm Qcn9000 Firmware, Qualcomm Qcn9074 Firmware, Qualcomm Qcs405 Firmware, Qualcomm Qcs410 Firmware and 41 more.

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

Apply the vendor's patch.

## Is CVE-2021-30298 being exploited?

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

## Other vulnerabilities in Qualcomm Ar8031 Firmware

- [CVE-2025-27038](https://insights.sbomify.com/CVE-2025-27038/): Qualcomm Multiple Chipsets Use-After-Free (high 7.5, exploited in the wild)
- [CVE-2022-25729](https://insights.sbomify.com/CVE-2022-25729/): Improper Input Validation in MODEM (critical 9.8)
- [CVE-2022-25727](https://insights.sbomify.com/CVE-2022-25727/): Memory corruption in Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music (critical 9.8)
- [CVE-2021-30285](https://insights.sbomify.com/CVE-2021-30285/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (critical 9.3)
- [CVE-2021-30275](https://insights.sbomify.com/CVE-2021-30275/): Integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-30298 is a medium-severity memory corruption vulnerability in Qualcomm Ar8031 Firmware, published on 3 Jan 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-30298 in the wild and no public exploit code.

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

## Sources

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

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