# 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

> An integer overflow in the page alignment interface allows attackers to potentially execute code or cause denial of service on Qualcomm Snapdragon devices.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jan 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-687m-vvf2-78mq

## What is CVE-2021-30275?

CVE-2021-30275 is a critical 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 integer overflow in page alignment interface due to lack of address and size validation before alignment in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 127 products.


Products: Qualcomm Ar8031 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Csr8811 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Csrb31024 Firmware, Qualcomm Fsm10055 Firmware, Qualcomm Fsm10056 Firmware, Qualcomm Ipq6000 Firmware, Qualcomm Ipq6005 Firmware, Qualcomm Ipq6010 Firmware, Qualcomm Ipq6018 Firmware, Qualcomm Ipq6028 Firmware, Qualcomm Mdm9150 Firmware, Qualcomm Mdm9205 Firmware, Qualcomm Qca4004 Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6390 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6426 Firmware and 107 more.

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

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

## Is CVE-2021-30275 being exploited?

There is no known exploitation of CVE-2021-30275 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-30274](https://insights.sbomify.com/CVE-2021-30274/): Integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (high 8.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-30275 is a critical 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-30275 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-30275/ (Markdown: https://insights.sbomify.com/CVE-2021-30275/index.md)
```

## Sources

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

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