# CVE-2017-6899: Null dereference in n/a

> Attackers can crash Android MSM devices by writing to a debug interface, causing a denial of service via null pointer dereference.

- **Severity:** Medium 6.2 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** Yes
- **Published:** 16 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gf68-qxhp-mhcf

## What is CVE-2017-6899?

CVE-2017-6899 is a medium-severity vulnerability in n/a, published on 16 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The msm_bus_dbg_update_request_write function in drivers/platform/msm/msm_bus/msm_bus_dbg.c in android_kernel_huawei_msm8916 through 2017-06-16 in LineageOS, and possibly other kernels for MSM devices, allows attackers to cause a denial of service (NULL pointer dereference and device crash) via a crafted /sys/kernel/debug/msm-bus-dbg/client-data/update-request write request.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2017-6899?

It affects 1 product.


Products: Lineageos Lineageos.

## How do I fix CVE-2017-6899?

Apply the vendor's patch.

## Is CVE-2017-6899 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-1010221](https://insights.sbomify.com/CVE-2019-1010221/): Privilege escalation in LineageOS (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6899 and fix it if it is affected.

What it is: CVE-2017-6899 is a medium-severity vulnerability in n/a, published on 16 Jun 2017. 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-2017-6899 in the wild and no public exploit code.

Affected product: n/a. 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-2017-6899/ (Markdown: https://insights.sbomify.com/CVE-2017-6899/index.md)
```

## Sources

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

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