# CVE-2017-18302: Race condition in Snapdragon Automobile, Snapdragon Mobile

> A race condition in Qualcomm Snapdragon SoCs allows arbitrary writes to Trusted Zone kernel memory, enabling code execution and privilege escalation.

- **Severity:** Medium 4.7 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **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:** 20 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4mmr-2wxr-3cr2

## What is CVE-2017-18302?

CVE-2017-18302 is a medium-severity vulnerability in Qualcomm Msm8996au Firmware, published on 20 Sep 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Snapdragon (Automobile ,Mobile) in version MSM8996AU, SD 425, SD 427, SD 430, SD 435, SD 450, SD 625, SD 650/52, SD 820, SD 820A, SD 835, SDA660, SDM429, SDM439, SDM630, SDM632, SDM636, SDM660, Snapdragon_High_Med_2016, a crafted HLOS client can modify the structure in memory passed to a QSEE application between the time of check and the time of use, resulting in arbitrary writes to TZ kernel memory regions.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2017-18302?

It affects 19 products.


Products: Qualcomm Msm8996au Firmware, Qualcomm Sd425 Firmware, Qualcomm Sd427 Firmware, Qualcomm Sd430 Firmware, Qualcomm Sd435 Firmware, Qualcomm Sd450 Firmware, Qualcomm Sd625 Firmware, Qualcomm Sd650 Firmware, Qualcomm Sd652 Firmware, Qualcomm Sd820 Firmware, Qualcomm Sd820a Firmware, Qualcomm Sd835 Firmware, Qualcomm Sda660 Firmware, Qualcomm Sdm429 Firmware, Qualcomm Sdm439 Firmware, Qualcomm Sdm630 Firmware, Qualcomm Sdm632 Firmware, Qualcomm Sdm636 Firmware, Qualcomm Sdm660 Firmware.

## How do I fix CVE-2017-18302?

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

## Is CVE-2017-18302 being exploited?

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

## Other vulnerabilities in Qualcomm Msm8996au Firmware

- [CVE-2017-18318](https://insights.sbomify.com/CVE-2017-18318/): Security feature bypass in Snapdragon Automobile, Snapdragon Mobile (critical 9.8)
- [CVE-2024-45555](https://insights.sbomify.com/CVE-2024-45555/): Integer Overflow to Buffer Overflow in Automotive OS Platform (high 8.4)
- [CVE-2022-33282](https://insights.sbomify.com/CVE-2022-33282/): Integer overflow to buffer overflow in Automotive Multimedia (high 8.4)
- [CVE-2022-25680](https://insights.sbomify.com/CVE-2022-25680/): Memory corruption in Snapdragon Auto (high 8.4)
- [CVE-2024-53030](https://insights.sbomify.com/CVE-2024-53030/): Improper Input Validation in Automotive OS Platform (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-18302 and fix it if it is affected.

What it is: CVE-2017-18302 is a medium-severity vulnerability in Qualcomm Msm8996au Firmware, published on 20 Sep 2018. 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-2017-18302 in the wild and no public exploit code.

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

## Sources

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

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