# CVE-2021-35081: Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music

> Buffer overflow in Qualcomm Snapdragon firmware allows attackers to execute arbitrary code or escalate privileges via malicious Wi-Fi beacon frames.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Jun 2022
- **Updated:** 4 Aug 2024
- **Also known as:** 3028274, A-213239834, ASB-A-213239834, GHSA-x57w-hccr-c6x7

## What is CVE-2021-35081?

CVE-2021-35081 is a critical memory corruption vulnerability in Qualcomm Aqt1000 Firmware, published on 14 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Possible buffer overflow due to improper validation of SSID length received from beacon or probe response during an IBSS session in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music

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

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

It affects 73 products.


Products: Qualcomm Aqt1000 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Qca6390 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6564 Firmware, Qualcomm Qca6564au Firmware, Qualcomm Qca6574a Firmware, Qualcomm Qca8081 Firmware, Qualcomm Qca8337 Firmware, Qualcomm Qcm2290 Firmware, Qualcomm Qcm4290 Firmware, Qualcomm Qcm6125 Firmware, Qualcomm Qcm6490 Firmware, Qualcomm Qcn7605 Firmware, Qualcomm Qcn7606 Firmware, Qualcomm Qcs2290 Firmware, Qualcomm Qcs4290 Firmware, Qualcomm Qcs610 Firmware, Qualcomm Qcs6125 Firmware, Qualcomm Qcs6490 Firmware and 53 more.

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

Apply the vendor's patch.

## Is CVE-2021-35081 being exploited?

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

What it is: CVE-2021-35081 is a critical memory corruption vulnerability in Qualcomm Aqt1000 Firmware, published on 14 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-35081 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-35081/ (Markdown: https://insights.sbomify.com/CVE-2021-35081/index.md)
```

## Sources

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

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