# CVE-2019-14079: Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

> An uninitialized variable in the DMA driver causes kernel failure when unmapping an unmapped buffer, leading to denial of service on 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:** 5 Mar 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r5w6-vmvw-3856

## What is CVE-2019-14079?

CVE-2019-14079 is a high-severity vulnerability in Qualcomm Apq8009 Firmware, published on 5 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Access to the uninitialized variable when the driver tries to unmap the dma buffer of a request which was never mapped in the first place leading to kernel failure in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables in APQ8009, APQ8053, MDM9607, MDM9640, MSM8909W, MSM8953, QCA6574AU, QCS605, SDA845, SDM429, SDM429W, SDM439, SDM450, SDM632, SDM670, SDM710, SDM845, SDX24, SM8150, SXR1130

Weakness: CWE-908 (Use of Uninitialized Resource)

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

It affects 20 products.


Products: Qualcomm Apq8009 Firmware, Qualcomm Apq8053 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9640 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Msm8953 Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qcs605 Firmware, Qualcomm Sda845 Firmware, Qualcomm Sdm429 Firmware, Qualcomm Sdm429w Firmware, Qualcomm Sdm439 Firmware, Qualcomm Sdm450 Firmware, Qualcomm Sdm632 Firmware, Qualcomm Sdm670 Firmware, Qualcomm Sdm710 Firmware, Qualcomm Sdm845 Firmware, Qualcomm Sdx24 Firmware, Qualcomm Sm8150 Firmware, Qualcomm Sxr1130 Firmware.

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

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

## Is CVE-2019-14079 being exploited?

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

Public exploit code:

- USB device fuzzing on Android Phone (github_poc): https://github.com/parallelbeings/CVE-2019-14079

## 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-2019-14079 and fix it if it is affected.

What it is: CVE-2019-14079 is a high-severity vulnerability in Qualcomm Apq8009 Firmware, published on 5 Mar 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-2019-14079 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-2019-14079/ (Markdown: https://insights.sbomify.com/CVE-2019-14079/index.md)
```

## Sources

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

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