CVE-2019-9111
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_evtlog_filter_write in drivers/gpu/drm/msm/sde_dbg.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 in msm GPU driver's sde_evtlog_filter_write function allows a crafted application on a rooted Xiaomi MIX 3 device to crash the kernel (OOPS) by providing an unchecked count argument. The vulnerability exists in drivers/gpu/drm/msm/sde_dbg.c where missing bounds validation on the count parameter leads to the overflow and subsequent kernel panic.
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 system is a Xiaomi MIX 3 (codename Perseus) by reviewing /proc/cpuinfo, /system/build.prop, or using 'getprop ro.product.model'Affected if Device is a Xiaomi MIX 3 (Perseus)
-
Check kernel build dateRun 'uname -a' or check /proc/version to obtain the kernel build dateAffected if Kernel build date is on or before 2018-11-26
-
Verify vulnerable driver presenceCheck if /sys/kernel/debug/dri/0 exists or if the msm DRM driver is loaded via 'lsmod | grep msm' or checking /proc/modulesAffected if MSM GPU DRM driver is loaded and debug interface is accessible
-
Check sde_dbg.c driver versionLocate the sde_evtlog_filter_write function in the kernel source or compiled driver module to inspect bounds checking logic. This typically requires access to the kernel image or source code.Affected if The function lacks proper bounds validation on the count parameter
-
Confirm root access for exploitation contextThis vulnerability requires a rooted device to exploit. Check if the device has root privileges via 'su' command or root checker applications.Affected if Device is rooted - note that the vulnerability is only exploitable on rooted devices, but the vulnerable code may still exist on non-rooted devices
The environment is affected only if it is a Xiaomi MIX 3 (Perseus) device with a kernel build date on or before 2018-11-26 that contains the vulnerable msm GPU driver with the unpatched sde_evtlog_filter_write function lacking count bounds validation.
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 dataAdd proper bounds checking for the count argument in sde_evtlog_filter_write to validate input size before use, preventing integer overflow. This requires patching the Linux kernel driver code.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9111 — 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-9111 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