# CVE-2020-3648: Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

> Out-of-bounds write in Qualcomm Snapdragon DSP driver allows attackers to execute arbitrary code or escalate privileges via crafted user data.

- **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:** No
- **Published:** 8 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vxw3-96f4-67xp

## What is CVE-2020-3648?

CVE-2020-3648 is a high-severity memory corruption vulnerability in Qualcomm Msm8909w Firmware, published on 8 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

u'Possible out of bound write in DSP driver code due to lack of check of data received from user' in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in MSM8909W

Weakness: CWE-787 (Out-of-bounds Write), CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Qualcomm Msm8909w Firmware.

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

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

## Is CVE-2020-3648 being exploited?

There is no known exploitation of CVE-2020-3648 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-2020-3648 and fix it if it is affected.

What it is: CVE-2020-3648 is a high-severity memory corruption vulnerability in Qualcomm Msm8909w Firmware, published on 8 Sep 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-3648 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-2020-3648/ (Markdown: https://insights.sbomify.com/CVE-2020-3648/index.md)
```

## Sources

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

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