# CVE-2020-11160: Denial of service in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

> A resource leakage in Qualcomm Snapdragon firmware can lead to denial of service due to improper reference counting during client registration failures.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-37g9-8cjr-x358

## What is CVE-2020-11160?

CVE-2020-11160 is a medium-severity denial of service vulnerability in Qualcomm Apq8096au Firmware, published on 9 Jun 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Resource leakage issue during dci client registration due to reference count is not decremented if dci client registration fails in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 145 products.


Products: Qualcomm Apq8096au Firmware, Qualcomm Aqt1000 Firmware, Qualcomm Ar8031 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Pm215 Firmware, Qualcomm Pm3003a Firmware, Qualcomm Pm6125 Firmware, Qualcomm Pm6150 Firmware, Qualcomm Pm6150l Firmware, Qualcomm Pm640a Firmware, Qualcomm Pm640l Firmware, Qualcomm Pm640p Firmware, Qualcomm Pm8008 Firmware, Qualcomm Pm8009 Firmware, Qualcomm Pm8150 Firmware, Qualcomm Pm8150a Firmware, Qualcomm Pm8150b Firmware and 125 more.

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

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

## Is CVE-2020-11160 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8096au Firmware

- [CVE-2019-14045](https://insights.sbomify.com/CVE-2019-14045/): Memory corruption in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2017-14911](https://insights.sbomify.com/CVE-2017-14911/): Auth bypass in Snapdragon IoT, Snapdragon Mobile, Snapdragon Automobile (critical 9.8)
- [CVE-2020-11126](https://insights.sbomify.com/CVE-2020-11126/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (critical 9.1)
- [CVE-2022-33243](https://insights.sbomify.com/CVE-2022-33243/): Improper access control in Qualcomm IPC (high 8.4)
- [CVE-2022-22063](https://insights.sbomify.com/CVE-2022-22063/): Memory corruption in Core (high 8.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11160 is a medium-severity denial of service vulnerability in Qualcomm Apq8096au Firmware, published on 9 Jun 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-2020-11160 in the wild and no public exploit code.

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

## Sources

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

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