LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9399: In /proc/driver/wmt_dbg driver, there are several possible out of bounds writes.

In /proc/driver/wmt_dbg driver, there are several possible out of bounds writes. These 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-9399 is an Android kernel issue in the /proc/driver/wmt_dbg driver. A local attacker could exploit out-of-bounds writes to gain higher privileges. It is not described as remotely exploitable, and no active exploitation is cited in the provided sources.

Executive priority

Treat this as a high-priority legacy Android kernel exposure where vulnerable devices remain in service. Business urgency depends on fleet age, patch levels, and whether untrusted apps can run locally.

Technical view

The CVE describes several possible out-of-bounds writes in /proc/driver/wmt_dbg, classified as CWE-787. CVSS 3.1 is 7.8: 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 containing the vulnerable /proc/driver/wmt_dbg driver. The supplied affected data names Google Android Kernel but does not enumerate exact device models, kernel versions, or downstream OEM status.

Exploitation context

The CVSS vector indicates exploitation requires local access and some privileges, with no user interaction. The sources do not show CISA KEV listing or other evidence of active exploitation. Successful exploitation could elevate privileges to System-level execution.

Researcher notes

Evidence is narrow: the CVE states the vulnerable driver path, bug class, privilege impact, and CVSS vector. It does not provide exploit details, exact fixed versions, or OEM-specific exposure. Avoid assuming affected devices beyond sourced Android kernel context.

Mitigation direction

  • Review the Pixel June 2018 security bulletin for vendor guidance.
  • Apply applicable Android, Pixel, OEM, or kernel security updates.
  • Prioritize devices with untrusted local app execution risk.
  • Restrict deployment of outdated Android kernel images where feasible.
  • Monitor vendor advisories for exact affected build details.

Validation and detection

  • Inventory Android devices and kernel build levels.
  • Check whether /proc/driver/wmt_dbg exists on managed devices.
  • Confirm devices received the relevant June 2018 Pixel or OEM fixes.
  • Review EDR or MDM telemetry for abnormal local privilege escalation indicators.
  • Document unknown OEM exposure where vendor data is unavailable.
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-9399 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-9399Attack 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.