# CVE-2020-3613: Use after free in Snapdragon Compute, Snapdragon Mobile, Snapdragon Voice & Music

> A double free vulnerability in Qualcomm Snapdragon firmware allows attackers to execute arbitrary code or escalate privileges via memory corruption.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** Yes
- **Published:** 22 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** 2239987, A-148816706, ASB-A-148816706, GHSA-9j42-xg9h-9p2w

## What is CVE-2020-3613?

CVE-2020-3613 is a high-severity use after free vulnerability in Qualcomm Sm8150 Firmware, published on 22 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Double free issue in kernel memory mapping due to lack of memory protection mechanism in Snapdragon Compute, Snapdragon Mobile, Snapdragon Voice & Music in SM8150

Weakness: CWE-415 (Double Free)

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

It affects 1 product.


Products: Qualcomm Sm8150 Firmware.

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

Apply the vendor's patch.

## Is CVE-2020-3613 being exploited?

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

## Other vulnerabilities in Qualcomm Sm8150 Firmware

- [CVE-2019-14048](https://insights.sbomify.com/CVE-2019-14048/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-3613 is a high-severity use after free vulnerability in Qualcomm Sm8150 Firmware, published on 22 Jun 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-2020-3613 in the wild and no public exploit code.

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

## Sources

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

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