LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9400: In gt1x_debug_write_proc and gt1x_tool_write of drivers/input/touchscreen/mediatek/GT1151/gt1x_generic....

In gt1x_debug_write_proc and gt1x_tool_write of drivers/input/touchscreen/mediatek/GT1151/gt1x_generic.c and gt1x_tools.c, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-9400 is a local privilege escalation flaw in an Android kernel touchscreen driver. A local attacker with required privileges could trigger an out-of-bounds write and gain higher impact within the device. The source bundle does not show remote exploitation or active exploitation.

Executive priority

Handle as a high-priority mobile device hygiene issue where affected Android kernels are present. Business urgency is lower than remotely exploitable bugs, but elevated because successful exploitation can affect confidentiality, integrity, and availability on the device.

Technical view

The issue is CWE-787 in gt1x_debug_write_proc and gt1x_tool_write within MediaTek GT1151 touchscreen driver files. Missing bounds checks may allow an out-of-bounds write. CVSS 3.1 is 7.8, local attack vector, low complexity, low privileges, no user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to Android kernel builds that include the referenced MediaTek GT1151 touchscreen driver code. The bundle names Google Android Kernel and a Pixel June 2018 bulletin, but does not provide a complete device or OEM affected list.

Exploitation context

The bundle reports no user interaction requirement and local attack vector. It does not cite CISA KEV listing or any public active exploitation evidence. Treat exploitation status as unconfirmed, not known exploited.

Researcher notes

Evidence is sparse. The source identifies two driver functions and missing bounds checks but does not include patch details, affected OEM matrix, or exploit evidence. Validation should focus on kernel code presence and vendor patch confirmation.

Mitigation direction

  • Check Google and OEM guidance for CVE-2018-9400 applicability.
  • Apply vendor security updates for affected Android kernel builds.
  • Prioritize managed devices using MediaTek GT1151 touchscreen driver code.
  • Retire or isolate devices that cannot receive vendor kernel fixes.
  • Limit untrusted local app execution on potentially affected devices.

Validation and detection

  • Inventory Android devices and kernel builds in scope.
  • Check kernel source or SBOM for the GT1151 gt1x driver files.
  • Verify vendor patch level against the June 2018 Pixel bulletin or OEM equivalent.
  • Confirm whether device vendors list CVE-2018-9400 as fixed.
  • Track exceptions for unsupported devices lacking vendor confirmation.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-9400 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2018-9400Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroidKernelunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.