CVE-2025-36902
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 syna_cdev_ioctl_store_pid() of syna_tcm2_sysfs.c, there is a possible out of bounds write due to a heap buffer overflow. This could lead to 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 confidenceHeap buffer overflow vulnerability in syna_cdev_ioctl_store_pid() function of the syna_tcm2_sysfs.c driver allows a local attacker with System execution privileges to perform out-of-bounds write, potentially achieving local privilege escalation.
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.1/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 Synaptics touch controller presenceCheck /sys/class/input/ or /dev/ for syna_tcm or synaptics related device nodes, or check dmesg for 'syna_tcm' or 'synaptics' driver loading messagesAffected if The device has a Synaptics touch controller using the syna_tcm2 driver
-
Verify the vulnerable driver function existsCheck if the kernel module or driver includes the syna_cdev_ioctl_store_pid function by examining /sys/module/syna_tcm2* (if modular) or checking driver sysfs exports under /sys/class/touchscreen/Affected if The syna_tcm2 driver with the syna_cdev_ioctl_store_pid function is present and loaded
-
Confirm System-level execution contextVerify the attacker would need System (not root) privileges - check if the device grants any third-party apps System-level permissions or if the touch controller driver ioctl interface is accessible from untrusted contextsAffected if The driver ioctl interface at /dev/syna_tcm* is accessible to processes running as System user or with System permissions
-
Check kernel version against Android all versionsRun 'getprop ro.build.version.release' or 'cat /proc/version' to determine Android kernel version - note that the vulnerability affects all versions meaning no version is safe if the driver is presentAffected if The device runs any version of Google Android AND has the vulnerable Synaptics driver loaded
A user is affected if their Android device has a Synaptics touch controller using the syna_tcm2 driver with the syna_cdev_ioctl_store_pid() function present, regardless of Android version since the summary indicates all versions are affected.
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 vendor-provided patches or update to a fixed version of the synaptics touch controller driver/kernel module that addresses the heap buffer overflow in syna_cdev_ioctl_store_pid().
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36902 — 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-2025-36902 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