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

> A null pointer dereference in Qualcomm Snapdragon components can cause memory corruption and denial of service during buffer allocation.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 May 2021
- **Updated:** 4 Aug 2024
- **Also known as:** 2740910, A-172354397, GHSA-938v-qrv3-mj9q, PUB-A-172354397

## What is CVE-2020-11254?

CVE-2020-11254 is a medium-severity vulnerability in Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Mobile, published on 7 May 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Memory corruption during buffer allocation due to dereferencing session ctx pointer without checking if pointer is valid in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Mobile

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 121 products.


Products: Qualcomm Pm6150a, Qualcomm Pm6150l, Qualcomm Pm6350, Qualcomm Pm660, Qualcomm Pm660l, Qualcomm Pm7250b, Qualcomm Pm8008, Qualcomm Pm8009, Qualcomm Pm8350, Qualcomm Pm8350b, Qualcomm Pm8350bh, Qualcomm Pm8350c, Qualcomm Pmk8003, Qualcomm Pmk8350, Qualcomm Pmm6155au, Qualcomm Pmm8155au, Qualcomm Pmm8195au, Qualcomm Pmr735a, Qualcomm Pmr735b, Qualcomm Qat3516 and 101 more.

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

Apply the vendor's patch.

## Is CVE-2020-11254 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11254 is a medium-severity vulnerability in Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Mobile, published on 7 May 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-11254 in the wild and no public exploit code.

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

## Sources

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

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