CVE-2019-9276
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 · uneditedIn the Android kernel in the synaptics_dsx_htc touchscreen driver there is a possible out of bounds write due to a use after free. This could lead to a local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.
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 confidenceUse-after-free vulnerability in the synaptics_dsx_htc touchscreen driver within the Android kernel leads to an out-of-bounds write, enabling local privilege escalation to System level without user interaction.
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 dataall versionsCVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 if synaptics_dsx_htc driver is presentCheck the kernel module directory or driver files for 'synaptics_dsx_htc' (e.g., look for .ko files or driver entries in /proc/kallsyms, /sys/module, or device-specific driver paths)Affected if The driver file or module named synaptics_dsx_htc exists on the device
-
Verify the Android kernel versionRun 'uname -r' or check /proc/version to obtain the kernel version, then compare against the version that includes the CVE-2019-9276 patch (contact device manufacturer for patch date)Affected if The kernel version predates the CVE-2019-9276 security patch for this driver
-
Check if touchscreen uses the affected driverInspect /sys/class/input or /sys/bus/platform/devices for the touchscreen driver binding, or check dmesg for 'synaptics_dsx_htc' driver initialization messagesAffected if The device touchscreen is initialized using the synaptics_dsx_htc driver
-
Look for use-after-free indicators in kernel logsReview dmesg or kernel log buffers for memory corruption, driver crashes, or unexpected behavior related to the touchscreen driverAffected if Kernel logs show memory corruption or driver instability involving synaptics_dsx_htc that may indicate exploitation of this flaw
The device is affected if it contains the synaptics_dsx_htc touchscreen driver and is running an Android kernel version that predates the CVE-2019-9276 security patch.
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 the appropriate Android kernel security patch for CVE-2019-9276; affected devices require a kernel update that addresses the use-after-free in the touchscreen driver.
- Consultation3.0 h
- Implementation6.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,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9276 — 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-9276 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