CVE-2018-19939
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 Goodix GT9xx touchscreen driver for custom Linux kernels on Xiaomi daisy-o-oss and daisy-p-oss as used in Mi A2 Lite and RedMi6 pro devices through 2018-08-27 has a NULL pointer dereference in kfree after a kmalloc failure in gtp_read_Color in drivers/input/touchscreen/gt917d/gt9xx.c.
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 · high confidenceThe Goodix GT9xx touchscreen driver for custom Linux kernels on Xiaomi Mi A2 Lite and RedMi 6 Pro devices contains a NULL pointer dereference vulnerability in the gtp_read_Color function. The flaw occurs when memory allocation (kmalloc) fails, leading to improper error handling that results in a NULL pointer dereference when the code attempts to use the failed allocation pointer.
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-08-27<= 2018-08-27CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 target device is a Xiaomi Mi A2 Lite or Redmi 6 Pro/Redmi 6 by reviewing system information in Settings > About Phone or using 'getprop ro.product.model' via ADBAffected if Device model matches Mi A2 Lite or Redmi 6/Redmi 6 Pro
-
Check firmware build dateRetrieve the firmware/build date from Settings > About Phone > Build Number or via 'getprop ro.build.date' command through ADBAffected if Build date is on or before August 27, 2018 (format: '27 Aug 2018' or '2018-08-27')
-
Verify Goodix GT9xx touchscreen driver is presentCheck for the Goodix driver module by running 'ls -la /system/lib/modules/' or checking /proc/modules for 'gt9xx' or 'goodix' entries via ADB shellAffected if Goodix GT9xx touchscreen driver is loaded on the device
-
Confirm custom kernel usageCheck kernel version via 'uname -a' or 'getprop ro.kernel.version' to determine if a custom Linux kernel is in use on the deviceAffected if Device is running a custom-built Linux kernel (not stock MIUI firmware)
User is likely affected if the device is a Xiaomi Mi A2 Lite or Redmi 6/Redmi 6 Pro with firmware build date on or before August 27, 2018, and the Goodix GT9xx touchscreen driver 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 dataUsers should obtain updated kernel/firmware from Xiaomi or apply the vendor patch that adds proper error checking and prevents the NULL pointer dereference after kmalloc failure. Until then, avoid using touchscreen functionality in affected configurations.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19939 — 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-2018-19939 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