LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9396: In rpc_msg_handler and related handlers of drivers/misc/mediatek/eccci/port_rpc.c, there is a possible out...

In rpc_msg_handler and related handlers of drivers/misc/mediatek/eccci/port_rpc.c, there is a possible out of bounds write due to an incorrect 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
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-9396 is a high-severity Android kernel flaw in a MediaTek ECCCI RPC driver path. A local attacker with existing low privileges could potentially gain higher privileges without user interaction. The sources do not identify active exploitation or specific affected device models.

Executive priority

Treat as a high-priority mobile platform hygiene issue, especially for fleets with older MediaTek-based Android devices. Business urgency depends on whether affected kernel builds remain in use and patchable.

Technical view

The issue is an out-of-bounds write caused by an incorrect bounds check in rpc_msg_handler and related handlers in drivers/misc/mediatek/eccci/port_rpc.c. It is classified as CWE-787 with CVSS 3.1 score 7.8: local, low complexity, low privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on Android kernel builds that include the MediaTek ECCCI port_rpc driver and lack the relevant Android/Pixel security bulletin fixes. The provided sources do not enumerate exact devices, kernel branches, or OEM patch status.

Exploitation context

The CVE requires local access with low privileges and no user interaction. KEV status is false, and the provided sources do not claim active exploitation or public exploit availability.

Researcher notes

The source bundle supports high severity but lacks commit details, exact vulnerable version ranges, and OEM-specific applicability. Avoid assuming all Android devices are affected; validate presence of the MediaTek ECCCI port_rpc driver and patch lineage.

Mitigation direction

  • Apply relevant Android or OEM security updates for affected kernel builds.
  • Check vendor guidance for device-specific patch availability and timelines.
  • Prioritize managed Android devices using MediaTek modem/kernel components.
  • Retire or isolate devices that cannot receive security updates.

Validation and detection

  • Inventory Android devices and kernel builds using MediaTek ECCCI components.
  • Compare device patch levels against the referenced Pixel June 2018 bulletin.
  • Confirm OEM kernel source or advisories include the port_rpc bounds-check fix.
  • Review fleet telemetry for unexplained local privilege escalation indicators.
Prepared
Confidence
medium
Sources
3

Public sources used

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-9396 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-9396Attack 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroidKernelunaffected
Weakness

CWE details

CWE-787

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.

Open CWE intelligenceSame-CWE CVEs