# CVE-2021-30316: Memory corruption in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

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

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/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:** 20 Oct 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-6p95-gmgm-vw9w

## What is CVE-2021-30316?

CVE-2021-30316 is a high-severity memory corruption vulnerability in Qualcomm Ar8031 Firmware, published on 20 Oct 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 memory access due to improper boundary check while creating HSYNC fence in Snapdragon Auto, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 77 products.


Products: Qualcomm Ar8031 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Fsm10055 Firmware, Qualcomm Fsm10056 Firmware, Qualcomm Mdm9150 Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6564a Firmware, Qualcomm Qca6564au Firmware, Qualcomm Qca6574 Firmware, Qualcomm Qca6574a Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qca6584au Firmware, Qualcomm Qca6595 Firmware, Qualcomm Qca6595au Firmware, Qualcomm Qca6696 Firmware, Qualcomm Qca9377 Firmware, Qualcomm Qcm6490 Firmware, Qualcomm Qcs405 Firmware and 57 more.

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

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

## Is CVE-2021-30316 being exploited?

There is no known exploitation of CVE-2021-30316 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-30316 and fix it if it is affected.

What it is: CVE-2021-30316 is a high-severity memory corruption vulnerability in Qualcomm Ar8031 Firmware, published on 20 Oct 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-30316 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-30316/ (Markdown: https://insights.sbomify.com/CVE-2021-30316/index.md)
```

## Sources

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

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