# CVE-2020-11273: Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Mobile

> A missing null check in Qualcomm Snapdragon firmware allows attackers to cause a denial of service via null pointer dereference.

- **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-6jqw-mq9c-9fwx

## What is CVE-2020-11273?

CVE-2020-11273 is a high-severity vulnerability in Qualcomm Csrb31024 Firmware, published on 7 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Histogram type KPI was teardown with the assumption of the existence of histogram binning info and will lead to null pointer access when histogram binning info is missing due to lack of null check in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Mobile

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 178 products.


Products: Qualcomm Csrb31024 Firmware, Qualcomm Pm3003a Firmware, Qualcomm Pm6150a Firmware, Qualcomm Pm6150l Firmware, Qualcomm Pm6350 Firmware, Qualcomm Pm7150a Firmware, Qualcomm Pm7150l Firmware, Qualcomm Pm7250 Firmware, Qualcomm Pm7250b Firmware, Qualcomm Pm8005 Firmware, Qualcomm Pm8008 Firmware, Qualcomm Pm8009 Firmware, Qualcomm Pm8150a Firmware, Qualcomm Pm8150b Firmware, Qualcomm Pm8150c Firmware, Qualcomm Pm8150l Firmware, Qualcomm Pm8250 Firmware, Qualcomm Pm8350 Firmware, Qualcomm Pm8350b Firmware, Qualcomm Pm8350bh Firmware and 158 more.

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

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

## Is CVE-2020-11273 being exploited?

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

## Other vulnerabilities in Qualcomm Csrb31024 Firmware

- [CVE-2020-11236](https://insights.sbomify.com/CVE-2020-11236/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Mobile (high 8.4)
- [CVE-2020-11237](https://insights.sbomify.com/CVE-2020-11237/): Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Mobile (high 8.4)
- [CVE-2024-43066](https://insights.sbomify.com/CVE-2024-43066/): Use After Free in HLOS (high 7.8)
- [CVE-2023-28572](https://insights.sbomify.com/CVE-2023-28572/): Buffer Over-read in WLAN HOST (medium 6.6)
- [CVE-2020-11186](https://insights.sbomify.com/CVE-2020-11186/): Denial of service in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Mobile (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11273 is a high-severity vulnerability in Qualcomm Csrb31024 Firmware, 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-11273 in the wild and no public exploit code.

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

## Sources

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

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