# CVE-2019-10207: Null dereference in kernel

> A local attacker with write permissions to Bluetooth hardware can crash the Linux kernel via a crafted ioctl call.

- **Severity:** Medium 4.7 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/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:** Yes
- **Published:** 25 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-10207, GHSA-frg3-qcjh-fvr9, UBUNTU-CVE-2019-10207

## What is CVE-2019-10207?

CVE-2019-10207 is a medium-severity vulnerability in Linux kernel, published on 25 Nov 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in the Linux kernel's Bluetooth implementation of UART, all versions kernel 3.x.x before 4.18.0 and kernel 5.x.x. An attacker with local access and write permissions to the Bluetooth hardware could use this flaw to issue a specially crafted ioctl function call and cause the system to crash.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2019-10207 being exploited?

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

Public exploit code:

- PoC for CVE-2019-10207 (github_poc): https://github.com/butterflyhack/CVE-2019-10207

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10207 is a medium-severity vulnerability in Linux kernel, published on 25 Nov 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-2019-10207 in the wild and no public exploit code.

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

## Sources

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

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