# CVE-2019-1992: Use after free in Android

> A race condition in Android's Bluetooth stack allows remote code execution via a use-after-free vulnerability, requiring user interaction.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Feb 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-fpv6-vj3v-hf55

## What is CVE-2019-1992?

CVE-2019-1992 is a high-severity use after free vulnerability in Google Android, published on 28 Feb 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

In bta_hl_sdp_query_results of bta_hl_main.cc, there is a possible use-after-free due to a race condition. This could lead to remote code execution with no additional execution privileges needed. User interaction is needed for exploitation. Product: Android. Versions: Android-7.0 Android-7.1.1 Android-7.1.2 Android-8.0 Android-8.1 Android-9. Android ID: A-116222069.

Weakness: CWE-416 (Use After Free), CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2019-1992?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2019-1992?

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

## Is CVE-2019-1992 being exploited?

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

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1992 and fix it if it is affected.

What it is: CVE-2019-1992 is a high-severity use after free vulnerability in Google Android, published on 28 Feb 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-1992 in the wild and no public exploit code.

Affected product: Google Android. 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-2019-1992/ (Markdown: https://insights.sbomify.com/CVE-2019-1992/index.md)
```

## Sources

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

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