# CVE-2020-11268: Denial of service in Snapdragon Auto, Snapdragon Mobile

> A crafted SIB1 message can cause a User Equipment reset, leading to denial of service 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:** 7 May 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-v2v9-v6h2-84q9

## What is CVE-2020-11268?

CVE-2020-11268 is a high-severity denial of service vulnerability in Qualcomm, Inc. Snapdragon Auto, Snapdragon Mobile, published on 7 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Potential UE reset while decoding a crafted Sib1 or SIB1 that schedules unsupported SIBs and can lead to denial of service in Snapdragon Auto, Snapdragon Mobile

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2020-11268?

It affects 86 products.


Products: Qualcomm Apq8009, Qualcomm Apq8016, Qualcomm Apq8074, Qualcomm Apq8084, Qualcomm Apq8094, Qualcomm Ar6003, Qualcomm Mdm8215, Qualcomm Mdm8215m, Qualcomm Mdm8615m, Qualcomm Mdm9215, Qualcomm Mdm9235m, Qualcomm Mdm9310, Qualcomm Mdm9609, Qualcomm Mdm9615, Qualcomm Mdm9615m, Qualcomm Mdm9635m, Qualcomm Mdm9640, Qualcomm Mdm9645, Qualcomm Msm8108, Qualcomm Msm8208 and 66 more.

## How do I fix CVE-2020-11268?

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

## Is CVE-2020-11268 being exploited?

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

## Other vulnerabilities in Qualcomm, Inc. Snapdragon Auto, Snapdragon Mobile

- [CVE-2020-11283](https://insights.sbomify.com/CVE-2020-11283/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2020-11136](https://insights.sbomify.com/CVE-2020-11136/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2020-11137](https://insights.sbomify.com/CVE-2020-11137/): Integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2020-11138](https://insights.sbomify.com/CVE-2020-11138/): Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking (critical 9.8)
- [CVE-2020-11143](https://insights.sbomify.com/CVE-2020-11143/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11268 and fix it if it is affected.

What it is: CVE-2020-11268 is a high-severity denial of service vulnerability in Qualcomm, Inc. Snapdragon Auto, Snapdragon Mobile, published on 7 May 2021. 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-2020-11268 in the wild and no public exploit code.

Affected product: Qualcomm, Inc. Snapdragon Auto, Snapdragon Mobile. 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-2020-11268/ (Markdown: https://insights.sbomify.com/CVE-2020-11268/index.md)
```

## Sources

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

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