LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9398: In fm_set_stat of mediatek FM radio driver, there is a possible OOB write due to improper input validat...

In fm_set_stat of mediatek FM radio driver, there is a possible OOB write due to improper input validation. 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-9398 is a high-severity Android kernel issue in the MediaTek FM radio driver. Bad input validation could allow an out-of-bounds write and local privilege escalation. The sources do not show remote exploitation or active exploitation evidence.

Executive priority

Treat as high priority for fleets containing older or unpatched MediaTek-based Android devices. Business urgency is lower where devices are current, vendor-supported, and patched beyond June 2018.

Technical view

The issue is in fm_set_stat in the MediaTek FM radio driver and is classified as CWE-787. CVSS 3.1 is 7.8: local attack vector, low complexity, low privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on Android devices using the affected MediaTek FM radio kernel driver. The bundle lists Google Android Kernel but does not enumerate device models, OEM builds, or non-Pixel patch availability.

Exploitation context

The provided sources describe local privilege escalation and no required user interaction. They do not provide evidence of public exploitation, CISA KEV listing, remote reachability, or weaponized exploit availability.

Researcher notes

Evidence is limited to the CVE record and Pixel security bulletin reference. Do not assume affected device models beyond the stated Android kernel and MediaTek FM radio driver context without OEM confirmation.

Mitigation direction

  • Apply the relevant Android or Pixel June 2018 security update where applicable.
  • Check OEM and chipset vendor guidance for affected MediaTek-based Android devices.
  • Prioritize replacement or isolation for devices that cannot receive kernel security updates.
  • Maintain controls limiting untrusted local app installation on exposed Android devices.

Validation and detection

  • Inventory Android devices for MediaTek chipsets and FM radio driver support.
  • Verify Android security patch level against the June 2018 Pixel bulletin guidance.
  • Check vendor firmware advisories for model-specific fixes or exposure statements.
  • Confirm vulnerable devices are not unmanaged or outside mobile device management coverage.
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-9398 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-9398Attack 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.