LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9390: In procfile_write of gl_proc.c, there is a possible out of bounds read of a function pointer due to an...

In procfile_write of gl_proc.c, there is a possible out of bounds read of a function pointer 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.

MediumCVSS 6.7Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-9390 is an Android Kernel issue involving an out-of-bounds read of a function pointer. It could allow local privilege escalation, but exploitation requires existing System-level privileges and no user interaction. The provided sources do not show active exploitation.

Executive priority

Treat as a moderate-priority legacy Android kernel issue. It is not remotely exploitable based on the bundle, but affected unpatched devices may face serious impact if an attacker already has high local privileges.

Technical view

The flaw is in procfile_write of gl_proc.c and is attributed to an incorrect bounds check, mapped to CWE-125. CVSS 3.1 is 6.7 with local access, low complexity, high privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure appears limited to Android Kernel builds containing the vulnerable gl_proc.c procfile_write logic. The bundle references the Pixel June 2018 security bulletin, but does not provide complete device, branch, or downstream vendor scope.

Exploitation context

The evidence supports local exploitation only, with high privileges required. There is no KEV listing and no cited source in the bundle reporting active exploitation in the wild.

Researcher notes

The provided record gives limited technical detail beyond function, file, weakness class, and CVSS vector. Avoid assuming broader Android or OEM exposure without vendor confirmation. No exploit status or specific patch commit is included in the bundle.

Mitigation direction

  • Check the Android or device vendor bulletin for CVE-2018-9390-specific guidance.
  • Apply vendor-provided Android or Pixel security updates that address this CVE.
  • Prioritize managed devices with outdated Android security patch levels.
  • Track downstream OEM firmware status where Pixel guidance does not apply.

Validation and detection

  • Inventory Android devices and kernel branches in scope.
  • Verify Android security patch levels against vendor guidance for June 2018 fixes.
  • Check whether maintained kernel sources include the vulnerable gl_proc.c logic.
  • Confirm no unsupported Android builds remain in production use.
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-125: 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-9390 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
Medium
CVSS
6.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:H/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
6.7CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H0.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.7Medium
CVSS 3.1 vector shape for CVE-2018-9390Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:H/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-125

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

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs