# CVE-2018-11939: Use after free in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile

> A use-after-free vulnerability in Qualcomm Snapdragon WLAN firmware allows attackers to execute arbitrary code or cause denial of service via multiple ACS scan requests.

- **Severity:** High 7.8 (`CVSS:3.0/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:** 14 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-p3hw-88vg-5j26

## What is CVE-2018-11939?

CVE-2018-11939 is a high-severity use after free vulnerability in Qualcomm Mdm9150 Firmware, published on 14 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Use after issue in WLAN function due to multiple ACS scan requests at a time in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in MDM9150, MDM9206, MDM9607, MDM9640, MDM9650, MSM8909W, QCA6574AU, SD 210/SD 212/SD 205, SD 615/16/SD 415, SD 625, SD 650/52, SD 820, SDX20

Weakness: CWE-416 (Use After Free)

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

It affects 18 products.


Products: Qualcomm Mdm9150 Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9640 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Qca6574au Firmware, Qualcomm Sd 205 Firmware, Qualcomm Sd 210 Firmware, Qualcomm Sd 212 Firmware, Qualcomm Sd 415 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 Sdx20 Firmware.

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

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

## Is CVE-2018-11939 being exploited?

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

## Other vulnerabilities in Qualcomm Mdm9150 Firmware

- [CVE-2019-10505](https://insights.sbomify.com/CVE-2019-10505/): Memory corruption in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-10542](https://insights.sbomify.com/CVE-2019-10542/): Memory corruption in Snapdragon Auto, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music (critical 9.8)
- [CVE-2019-2258](https://insights.sbomify.com/CVE-2019-2258/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)
- [CVE-2019-2283](https://insights.sbomify.com/CVE-2019-2283/): 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-2323](https://insights.sbomify.com/CVE-2019-2323/): Null dereference in Snapdragon Auto, Snapdragon Compute, 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-11939 and fix it if it is affected.

What it is: CVE-2018-11939 is a high-severity use after free vulnerability in Qualcomm Mdm9150 Firmware, published on 14 Jun 2019. 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-2018-11939 in the wild and no public exploit code.

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

## Sources

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

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