# CVE-2019-9112: Integer overflow in n/a

> A crafted application on a rooted Xiaomi device can trigger an integer overflow in the GPU driver, causing a system crash.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Feb 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-h27r-x6vq-qp4c

## What is CVE-2019-9112?

CVE-2019-9112 is a medium-severity vulnerability in n/a, published on 25 Feb 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The msm gpu driver for custom Linux kernels on the Xiaomi perseus-p-oss MIX 3 device through 2018-11-26 has an integer overflow and OOPS because of missing checks of the count argument in _sde_debugfs_conn_cmd_tx_write in drivers/gpu/drm/msm/sde/sde_connector.c. This is exploitable for a device crash via a syscall by a crafted application on a rooted device.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Micode Xiaomi Perseus-P-Oss.

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

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

## Is CVE-2019-9112 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-20787](https://insights.sbomify.com/CVE-2018-20787/): Integer overflow in n/a (medium 5.5)
- [CVE-2018-20788](https://insights.sbomify.com/CVE-2018-20788/): Integer overflow in n/a (medium 5.5)
- [CVE-2019-9111](https://insights.sbomify.com/CVE-2019-9111/): Integer overflow in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-9112 is a medium-severity vulnerability in n/a, published on 25 Feb 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-9112 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-9112/ (Markdown: https://insights.sbomify.com/CVE-2019-9112/index.md)
```

## Sources

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

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