LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9422: In get_futex_key of futex.c, there is a use-after-free due to improper locking.

In get_futex_key of futex.c, there is a use-after-free due to improper locking. This could lead to local escalation of privilege with no additional privileges needed. User interaction is not needed for exploitation. Product: Android Versions: Android kernel Android ID: A-74250718 References: Upstream kernel.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-9422 is an Android kernel flaw that could let a local attacker raise privileges on a device. It involves a use-after-free condition in futex handling caused by improper locking. The bundle does not provide CVSS scoring, affected build ranges, or evidence of active exploitation.

Executive priority

Treat this as a high-priority endpoint patching issue where affected Android or kernel-based systems are in scope. Business urgency is strongest for fleets with older devices, delayed OEM updates, or exposure to untrusted local apps.

Technical view

The issue is a use-after-free in get_futex_key in futex.c, attributed to improper locking. The stated impact is local escalation of privilege with no additional privileges and no user interaction required. The affected product listed is Android kernel; upstream Linux kernel references are cited, but version boundaries are not provided.

Likely exposure

Exposure is most likely on Android devices running affected kernel builds. Debian LTS and SUSE references indicate related Linux kernel tracking, but the supplied affected product list only names Android kernel. Confirm exposure against vendor kernel packages, Android security bulletins, and device patch levels.

Exploitation context

The source bundle says exploitation is local, needs no additional privileges, and requires no user interaction. CISA KEV status is false, and no cited source in the bundle states active exploitation or public exploit availability.

Researcher notes

Key gaps are CVSS data, exact affected kernel versions, fixed commit identifiers, and exploit maturity. The root cause and impact are clear, but exposure analysis depends on vendor-specific kernel provenance and patch backports.

Mitigation direction

  • Apply relevant Android or device-vendor security updates when available.
  • Check Linux distribution kernel advisories if managing non-Android kernels.
  • Prioritize devices allowing untrusted local app execution.
  • Restrict untrusted local code where patching is delayed.
  • Monitor vendor guidance for exact fixed kernel versions.

Validation and detection

  • Inventory Android devices and kernel build identifiers.
  • Compare device security patch levels with the July 2018 Android bulletin.
  • Check vendor advisories for CVE-2018-9422 or Android ID A-74250718.
  • Verify managed Linux kernels against Debian and SUSE advisory status.
  • Document systems where version applicability remains unclear.
Prepared
Confidence
medium
Sources
6

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.

cve · low confidence lookup

CVE-2018-9422 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Google Inc.AndroidAndroid kernelListed
Weakness

CWE details

No CWE listed

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