# CVE-2018-3590: Use after free in Snapdragon Mobile, Snapdragon Wear

> A use-after-free vulnerability in the Qualcomm RIL component allows attackers to execute arbitrary code or escalate privileges on affected Android devices.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 11 Apr 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-73qx-88cc-gwvw

## What is CVE-2018-3590?

CVE-2018-3590 is a critical use after free vulnerability in Qualcomm Msm8909w Firmware, published on 11 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Android before security patch level 2018-04-05 on Qualcomm Snapdragon Mobile and Snapdragon Wear MSM8909W, SD 210/SD 212/SD 205, SD 450, SD 615/16/SD 415, SD 625, SD 650/52, SD 820, SD 835, SD 845, a Use After Free condition can occur in RIL while handling requests from Android.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2018-3590?

It affects 14 products.


Products: Qualcomm Msm8909w Firmware, Qualcomm Sd 205 Firmware, Qualcomm Sd 210 Firmware, Qualcomm Sd 212 Firmware, Qualcomm Sd 415 Firmware, Qualcomm Sd 450 Firmware, Qualcomm Sd 615 Firmware, Qualcomm Sd 616 Firmware, Qualcomm Sd 625 Firmware, Qualcomm Sd 650 Firmware, Qualcomm Sd 652 Firmware, Qualcomm Sd 820 Firmware, Qualcomm Sd 835 Firmware, Qualcomm Sd 845 Firmware.

## How do I fix CVE-2018-3590?

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

## Is CVE-2018-3590 being exploited?

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

## Other vulnerabilities in Qualcomm Msm8909w Firmware

- [CVE-2019-2285](https://insights.sbomify.com/CVE-2019-2285/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-10509](https://insights.sbomify.com/CVE-2019-10509/): Use after free in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-10538](https://insights.sbomify.com/CVE-2019-10538/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-2255](https://insights.sbomify.com/CVE-2019-2255/): Code injection in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-2259](https://insights.sbomify.com/CVE-2019-2259/): Denial of service in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-3590 and fix it if it is affected.

What it is: CVE-2018-3590 is a critical use after free vulnerability in Qualcomm Msm8909w Firmware, published on 11 Apr 2018. 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-2018-3590 in the wild and no public exploit code.

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

## Sources

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

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