CVE-2019-9112
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceInteger overflow vulnerability in the MSM GPU driver's debugfs write function (_sde_debugfs_conn_cmd_tx_write) in sde_connector.c. The count argument is not validated before use in memory operations, leading to an OOPS (kernel panic) when the overflow occurs during the copy operation. Exploitation requires a rooted device and a crafted syscall to trigger the crash.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2018-11-26CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device modelCheck if the device is a Xiaomi Perseus P model. On the device, run 'getprop ro.product.model' or check the device packaging/documentation.Affected if Device is a Xiaomi Perseus P or variant with MSM GPU driver
-
Check kernel build dateRun 'getprop ro.build.date' or check '/proc/version' to determine the kernel build timestamp. Compare the date to 2018-11-26.Affected if Build date is on or before 2018-11-26 (vulnerable period)
-
Verify MSM GPU driver presenceCheck for the SDE connector driver module or kernel symbol. Run 'ls /sys/class/drm/' or check '/proc/kallsyms' for 'sde_connector' or '_sde_debugfs_conn_cmd_tx_write' entries.Affected if MSM GPU SDE connector driver is loaded in the kernel
-
Confirm debugfs accessCheck if debugfs is mounted by running 'mount | grep debugfs' or 'ls /sys/kernel/debug/'. The debugfs interface must be accessible for the vulnerable function to be triggered.Affected if Debugfs is mounted and accessible (typically at /sys/kernel/debug or /d/)
The device is affected if it is a Xiaomi Perseus P with a kernel build date on or before 2018-11-26 and the MSM GPU SDE connector driver with the vulnerable debugfs interface is present.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply bounds checking on the count argument in _sde_debugfs_conn_cmd_tx_write to validate it does not exceed expected limits before performing memory operations. The fix is a driver-level code change in the MSM GPU subsystem.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9112 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-9112 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data