# CVE-2020-3696: Use after free in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking

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

- **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:** 2 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-f266-qj4w-xhj9

## What is CVE-2020-3696?

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

### Official description

u'Use after free while installing new security rule in ipcrtr as old one is deleted and this rule could still be in use for checking security permission for particular process' in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking in APQ8009, APQ8017, APQ8053, APQ8096AU, APQ8098, IPQ4019, IPQ6018, IPQ8064, IPQ8074, MDM9206, MDM9207C, MDM9607, MSM8905, MSM8909W, MSM8996AU, QCA4531, QCA6574AU, QCA9531, QCM2150, QCS605, SDM429W, SDX20, SDX24

Weakness: CWE-416 (Use After Free)

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

It affects 23 products.


Products: Qualcomm Apq8009 Firmware, Qualcomm Apq8017 Firmware, Qualcomm Apq8053 Firmware, Qualcomm Apq8096au Firmware, Qualcomm Apq8098 Firmware, Qualcomm Ipq4019 Firmware, Qualcomm Ipq6018 Firmware, Qualcomm Ipq8064 Firmware, Qualcomm Ipq8074 Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9207c Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Msm8905 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Msm8996au Firmware, Qualcomm Qca4531 Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qca9531 Firmware, Qualcomm Qcm2150 Firmware, Qualcomm Qcs605 Firmware and 3 more.

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

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

## Is CVE-2020-3696 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8009 Firmware

- [CVE-2021-1905](https://insights.sbomify.com/CVE-2021-1905/): Qualcomm Multiple Chipsets Use-After-Free (high 8.4, exploited in the wild)
- [CVE-2020-11261](https://insights.sbomify.com/CVE-2020-11261/): Qualcomm Multiple Chipsets Improper Input Validation (high 7.8, exploited in the wild)
- [CVE-2021-1906](https://insights.sbomify.com/CVE-2021-1906/): Qualcomm Multiple Chipsets Detection of Error Condition Without Action (medium 6.2, exploited in the wild)
- [CVE-2022-40510](https://insights.sbomify.com/CVE-2022-40510/): Buffer copy without checking size of input in Audio. (critical 9.8)
- [CVE-2022-22088](https://insights.sbomify.com/CVE-2022-22088/): Integer Overflow to Buffer Overflow in Bluetooth HOST (critical 9.8)

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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