LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9368: In mtkscoaudio debugfs there is a possible arbitrary kernel memory write due to missing bounds check and we...

In mtkscoaudio debugfs there is a possible arbitrary kernel memory write due to missing bounds check and weakened SELinux policies. 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
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a local Android privilege-escalation flaw in mtkscoaudio debugfs. A user or process already running with high privileges could write outside intended kernel memory bounds, potentially gaining system-level control. It is not remotely exploitable based on the supplied CVSS vector.

Executive priority

Treat this as a moderate-priority mobile fleet hygiene issue. It is not shown as internet-facing or actively exploited, but successful abuse could give deep device control after an attacker already has privileged local execution.

Technical view

CVE-2018-9368 is a CWE-787 out-of-bounds write in Android mtkscoaudio debugfs, attributed to missing bounds checks and weakened SELinux policy. 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 builds or SoC-specific firmware containing the vulnerable mtkscoaudio debugfs behavior and SELinux policy state. The supplied affected data names Google Android with SoCVersion but does not identify device models, Android releases, or chipset families.

Exploitation context

The sources describe local escalation of privilege requiring system execution privileges and no user interaction. The bundle marks KEV as false, and no cited source states active exploitation. Practical risk is highest on unpatched Android devices where an attacker has already achieved substantial local execution.

Researcher notes

The public record is sparse. Key missing details include exact SoC versions, device models, fixed build identifiers, and vendor-specific patch mapping. Avoid assuming broad Android exposure without confirming mtkscoaudio debugfs and policy conditions on target firmware.

Mitigation direction

  • Check Android Security Bulletin June 2018 and device vendor guidance for applicable fixes.
  • Prioritize updates on Android devices with relevant SoC-specific firmware exposure.
  • Confirm SELinux policy and debugfs exposure align with vendor-supported production configuration.
  • Retire or isolate devices that cannot receive applicable vendor security updates.

Validation and detection

  • Inventory Android device models, firmware versions, and security patch levels.
  • Map devices against the June 2018 Android bulletin and vendor advisories.
  • Review whether mtkscoaudio debugfs is present in authorized test environments.
  • Verify production builds do not use weakened SELinux policy configurations.
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-9368 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-9368Attack 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroidSoCVersionunaffected
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.