Security readout for executives and security teams
Plain-English summary
This is a local Android kernel privilege escalation issue in a MediaTek WMT device driver. A bounds-checking mistake could let an already-local attacker write outside an intended memory area. The source says no user interaction is needed, but exploitation is local and requires some privileges.
Executive priority
Treat this as a high-priority mobile platform hygiene issue where affected Android devices remain in service. Business urgency is highest for unmanaged, unsupported, or sensitive-use devices.
Technical view
CVE-2018-9397 is a CWE-787 out-of-bounds write in WMT_unlocked_ioctl in the MTK WMT device driver. The CVSS 3.1 score is 7.8, with local attack vector, low complexity, low privileges required, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure appears limited to Android kernel builds that include the affected MediaTek WMT driver code. The bundle does not identify specific device models, OEM firmware versions, or all Android releases affected.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. Exploitation is described as local, low-complexity, requiring privileges, and not requiring user interaction.
Researcher notes
Evidence is sparse: the bundle provides the vulnerable function, bug class, impact, CVSS, and Pixel bulletin reference, but not commit details, affected model lists, or proof of exploitation.
Mitigation direction
- Apply vendor Android firmware updates that include the June 2018 Pixel security bulletin fix.
- For non-Pixel devices, check OEM or chipset vendor advisories for incorporated fixes.
- Prioritize managed Android devices using MediaTek wireless connectivity components.
- Retire or isolate devices that cannot receive relevant security updates.
Validation and detection
- Inventory Android devices by OEM, model, chipset, kernel build, and security patch level.
- Check whether deployed firmware includes the June 2018 Android/Pixel bulletin fixes.
- Confirm whether the kernel contains the MTK WMT driver path referenced by the CVE.
- Review MDM telemetry for unsupported or stale Android security patch levels.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2018-9397 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://source.android.com/security/bulletin/pixel/2018-06-01CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.