# CVE-2021-30273: Denial of service in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Wearables

> An attacker can cause a denial of service via an assertion failure triggered by malformed IPv6 packets in Qualcomm Snapdragon devices.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jan 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-429m-4jmr-m854

## What is CVE-2021-30273?

CVE-2021-30273 is a high-severity denial of service vulnerability in Qualcomm Apq8009w Firmware, published on 3 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Possible assertion due to improper handling of IPV6 packet with invalid length in destination options header in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Wearables

Weakness: CWE-617 (Reachable Assertion)

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

It affects 74 products.


Products: Qualcomm Apq8009w Firmware, Qualcomm Apq8096au Firmware, Qualcomm Ar6003 Firmware, Qualcomm Csrb31024 Firmware, Qualcomm Mdm8207 Firmware, Qualcomm Mdm9205 Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9207 Firmware, Qualcomm Mdm9215 Firmware, Qualcomm Mdm9250 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9615 Firmware, Qualcomm Mdm9628 Firmware, Qualcomm Mdm9640 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Msm8996au Firmware, Qualcomm Qca4004 Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6564a Firmware and 54 more.

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

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

## Is CVE-2021-30273 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8009w Firmware

- [CVE-2021-30341](https://insights.sbomify.com/CVE-2021-30341/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Wearables (critical 9.8)
- [CVE-2021-35104](https://insights.sbomify.com/CVE-2021-35104/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2020-11307](https://insights.sbomify.com/CVE-2020-11307/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Wearables (critical 9.8)
- [CVE-2021-30342](https://insights.sbomify.com/CVE-2021-30342/): Race condition in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.1)
- [CVE-2021-30334](https://insights.sbomify.com/CVE-2021-30334/): Use after free in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wearables (high 8.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-30273 is a high-severity denial of service vulnerability in Qualcomm Apq8009w Firmware, published on 3 Jan 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-30273 in the wild and no public exploit code.

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

## Sources

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

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