LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9401: In many locations, there is a possible way to access kernel memory in user space due to an incorrect bounds...

In many locations, there is a possible way to access kernel memory in user space due to an incorrect bounds check. This could lead to local escalation of privilege with no additional 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

This Android kernel flaw could let someone with local device access gain higher privileges by exposing kernel memory to user space. It is not described as remotely exploitable in the provided sources, and no user interaction is required after local access exists.

Executive priority

Treat as high priority for Android fleets because successful abuse could give an attacker broad device control. Urgency is highest where devices are unpatched, BYOD-managed, or exposed to untrusted apps.

Technical view

CVE-2018-9401 is a high-severity Android Kernel issue involving incorrect bounds checks in multiple locations. The CVSS vector is local, low complexity, low privileges, no UI, unchanged scope, with high confidentiality, integrity, and availability impact.

Likely exposure

Potential exposure is Android devices running affected Android Kernel builds. The provided bundle does not identify specific device models, kernel branches, or vulnerable patch levels beyond the Pixel June 2018 bulletin reference.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not marked as CISA KEV. Exploitation requires local access or code execution context, not a network-only attack path.

Researcher notes

Evidence is limited to the CVE description, CVSS data, affected Android Kernel entry, and Pixel bulletin reference. The bundle does not provide patch commit details, proof-of-concept status, exploit telemetry, or precise version ranges.

Mitigation direction

  • Review the Google Pixel June 2018 security bulletin for vendor guidance.
  • Update affected Android or Pixel devices to vendor-fixed security patch levels.
  • Prioritize managed devices that allow untrusted local apps or sideloading.
  • Restrict installation of untrusted apps until patch status is confirmed.

Validation and detection

  • Inventory Android devices and record OS, vendor, and security patch levels.
  • Compare device patch levels against the Pixel June 2018 bulletin guidance.
  • Confirm whether devices use affected Android Kernel builds.
  • Track unsupported devices as residual exposure if patches are unavailable.
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-276: 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-9401 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-9401Attack 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
GoogleAndroidAndroid Kernelunaffected
Weakness

CWE details

CWE-276

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

CWE-276 · source CWE mapping

Incorrect Default Permissions

Incorrect Default Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs