# CVE-2019-8413: Null dereference in n/a

> A NULL pointer dereference in the Xiaomi MIX 2 kernel allows local attackers to crash the system via a specific ioctl call.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/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:** No
- **Published:** 17 Feb 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pp5x-p6q3-m325

## What is CVE-2019-8413?

CVE-2019-8413 is a medium-severity vulnerability in n/a, published on 17 Feb 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

On Xiaomi MIX 2 devices with the 4.4.78 kernel, a NULL pointer dereference in the ioctl interface of the device file /dev/elliptic1 or /dev/elliptic0 causes a system crash via IOCTL 0x4008c575 (aka decimal 1074316661).

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Mi Mi Mix 2 Firmware.

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

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

## Is CVE-2019-8413 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-8413 is a medium-severity vulnerability in n/a, published on 17 Feb 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-8413 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-2019-8413/ (Markdown: https://insights.sbomify.com/CVE-2019-8413/index.md)
```

## Sources

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

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