# CVE-2019-10616: Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking

> A null pointer dereference in Qualcomm Snapdragon firmware allows denial of service when SPDM commands are executed non-standardly in the TrustZone.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vvq9-3244-5g7w

## What is CVE-2019-10616?

CVE-2019-10616 is a medium-severity vulnerability in Qualcomm Apq8009 Firmware, published on 5 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Possibility of null pointer access if the SPDM commands are executed in the non-standard way in TZ. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking in APQ8009, APQ8016, MDM9150, MDM9206, MDM9607, MDM9650, MSM8905, MSM8909, MSM8909W, MSM8998, SA6155P, SDX24

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2019-10616?

It affects 12 products.


Products: Qualcomm Apq8009 Firmware, Qualcomm Apq8016 Firmware, Qualcomm Mdm9150 Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Msm8905 Firmware, Qualcomm Msm8909 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Msm8998 Firmware, Qualcomm Sa6155p Firmware, Qualcomm Sdx24 Firmware.

## How do I fix CVE-2019-10616?

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

## Is CVE-2019-10616 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8009 Firmware

- [CVE-2021-1905](https://insights.sbomify.com/CVE-2021-1905/): Qualcomm Multiple Chipsets Use-After-Free (high 8.4, exploited in the wild)
- [CVE-2020-11261](https://insights.sbomify.com/CVE-2020-11261/): Qualcomm Multiple Chipsets Improper Input Validation (high 7.8, exploited in the wild)
- [CVE-2021-1906](https://insights.sbomify.com/CVE-2021-1906/): Qualcomm Multiple Chipsets Detection of Error Condition Without Action (medium 6.2, exploited in the wild)
- [CVE-2022-40510](https://insights.sbomify.com/CVE-2022-40510/): Buffer copy without checking size of input in Audio. (critical 9.8)
- [CVE-2022-22088](https://insights.sbomify.com/CVE-2022-22088/): Integer Overflow to Buffer Overflow in Bluetooth HOST (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10616 and fix it if it is affected.

What it is: CVE-2019-10616 is a medium-severity vulnerability in Qualcomm Apq8009 Firmware, published on 5 Mar 2020. 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-2019-10616 in the wild and no public exploit code.

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

## Sources

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

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