# CVE-2021-35115: Use after free in Snapdragon Auto, Snapdragon Mobile

> A use-after-free vulnerability in Qualcomm Snapdragon firmware allows attackers to execute arbitrary code or escalate privileges via improper session handling.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Apr 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jvq8-92c5-22jw

## What is CVE-2021-35115?

CVE-2021-35115 is a high-severity use after free vulnerability in Qualcomm Apq8096au Firmware, published on 1 Apr 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper handling of multiple session supported by PVM backend can lead to use after free in Snapdragon Auto, Snapdragon Mobile

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2021-35115?

It affects 28 products.


Products: Qualcomm Apq8096au Firmware, Qualcomm Ar6003 Firmware, Qualcomm Mdm8215 Firmware, Qualcomm Mdm8215m Firmware, Qualcomm Mdm8615m Firmware, Qualcomm Mdm9215 Firmware, Qualcomm Mdm9310 Firmware, Qualcomm Mdm9615 Firmware, Qualcomm Mdm9615m Firmware, Qualcomm Msm8996au Firmware, Qualcomm Qca6564a Firmware, Qualcomm Qca6564au Firmware, Qualcomm Qca6574a Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qca6584au Firmware, Qualcomm Qca6696 Firmware, Qualcomm Sa6145p Firmware, Qualcomm Sa6150p Firmware, Qualcomm Sa6155p Firmware, Qualcomm Sa8145p Firmware and 8 more.

## How do I fix CVE-2021-35115?

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

## Is CVE-2021-35115 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8096au Firmware

- [CVE-2019-14045](https://insights.sbomify.com/CVE-2019-14045/): Memory corruption in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2017-14911](https://insights.sbomify.com/CVE-2017-14911/): Auth bypass in Snapdragon IoT, Snapdragon Mobile, Snapdragon Automobile (critical 9.8)
- [CVE-2020-11126](https://insights.sbomify.com/CVE-2020-11126/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (critical 9.1)
- [CVE-2022-33243](https://insights.sbomify.com/CVE-2022-33243/): Improper access control in Qualcomm IPC (high 8.4)
- [CVE-2022-22063](https://insights.sbomify.com/CVE-2022-22063/): Memory corruption in Core (high 8.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-35115 and fix it if it is affected.

What it is: CVE-2021-35115 is a high-severity use after free vulnerability in Qualcomm Apq8096au Firmware, published on 1 Apr 2022. 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-2021-35115 in the wild and no public exploit code.

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

## Sources

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

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