LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9393: In procfile_write of drivers/misc/mediatek/connectivity/wlan/gen2/os/linux/gl_proc.c, there is a possible O...

In procfile_write of drivers/misc/mediatek/connectivity/wlan/gen2/os/linux/gl_proc.c, there is a possible OOB 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-9393 is a high-severity Android Kernel issue in a MediaTek WLAN driver. A missing bounds check may allow memory corruption through an out-of-bounds write. The cited sources describe local privilege escalation risk, not remote compromise, and do not show active exploitation.

Executive priority

Treat as high priority for legacy Android fleets and embedded Android devices. Business urgency depends on whether vulnerable MediaTek WLAN kernel code remains deployed without the 2018 security update.

Technical view

The flaw is CWE-787 in procfile_write within drivers/misc/mediatek/connectivity/wlan/gen2/os/linux/gl_proc.c. The CVSS 3.1 score is 7.8: local attack vector, low complexity, low privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure appears limited to Android kernel builds containing the referenced MediaTek WLAN gen2 driver. The bundle does not identify exact device models, downstream vendor builds, or unsupported firmware status.

Exploitation context

The source bundle says exploitation is local and does not require user interaction. It also says System execution privileges are needed. KEV is false, and no cited source states active exploitation.

Researcher notes

Evidence is sparse. Sources identify the vulnerable function, file path, weakness class, and CVSS vector, but not exact patched commits, device models, or exploit artifacts. Avoid broad Android-wide exposure claims without firmware confirmation.

Mitigation direction

  • Review the Android/Pixel June 2018 security bulletin for vendor guidance.
  • Confirm affected Android kernel builds have received the relevant security update.
  • Prioritize unmanaged, unsupported, or vendor-stale Android devices for review.
  • Check OEM firmware advisories before assuming a device is fixed.

Validation and detection

  • Inventory Android devices and kernel build provenance.
  • Identify builds using the MediaTek WLAN gen2 driver path.
  • Compare device patch level against the June 2018 Android/Pixel bulletin.
  • Verify OEM firmware status for devices outside Google-managed updates.
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-9393 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-9393Attack 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.