LiveActive security incident?Get immediate response
CVE Record

CVE-2017-18059: In Android for MSM, Firefox OS for MSM, QRD Android, with all Android releases from CAF using the Linux ker...

In Android for MSM, Firefox OS for MSM, QRD Android, with all Android releases from CAF using the Linux kernel, improper input validation for vdev id in wma_scan_event_callback(), which is received from firmware, leads to potential out of bounds memory read.

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

Security readout for executives and security teams

Plain-English summary

This vulnerability is an out-of-bounds memory read in Qualcomm CAF-derived Android kernel WLAN code. A firmware-supplied virtual device identifier was not properly validated before use. Sources do not provide severity, affected device models, or exploit evidence, so urgency depends on whether your fleet includes CAF-based Android/MSM builds with the vulnerable WLAN driver.

Executive priority

Treat this as a targeted asset-mapping and patch-confirmation item, not a broad emergency. Business risk is uncertain because severity and exploitation evidence are missing, but kernel-level mobile platform flaws should not remain untracked in managed device fleets.

Technical view

CVE-2017-18059 affects Android for MSM, Firefox OS for MSM, QRD Android, and Android releases from CAF using the Linux kernel. The issue is improper input validation of a vdev id in wma_scan_event_callback(), received from firmware, causing a potential out-of-bounds memory read.

Likely exposure

Exposure is most likely in Qualcomm MSM/CAF-derived Android or Firefox OS builds using the affected Linux kernel WLAN code. The bundle does not identify specific commercial devices, versions, or CPEs, so teams must map downstream devices and kernel driver lineage.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not listed as KEV. The vulnerability involves firmware-provided scan event data reaching kernel WLAN code, but practical exploitability and attacker prerequisites are not established in the bundle.

Researcher notes

Focus on whether the deployed WLAN driver contains the vulnerable wma_scan_event_callback() logic and whether the CodeAurora commit is present downstream. Avoid assuming exploitability beyond the documented out-of-bounds read from improper firmware-supplied vdev id validation.

Mitigation direction

  • Check Android, Pixel, and device-vendor March 2018 security guidance.
  • Apply vendor firmware and OS updates that include the referenced WLAN fix.
  • Confirm downstream kernels include the CodeAurora validation change or equivalent.
  • Prioritize managed Qualcomm/CAF-based Android devices for patch verification.

Validation and detection

  • Inventory devices using Android for MSM, QRD Android, or CAF-derived kernels.
  • Check each device's Android security patch level and vendor bulletin coverage.
  • Review kernel WLAN driver source for the referenced vdev id validation fix.
  • Track unsupported devices separately if vendor patch status cannot be confirmed.
Prepared
Confidence
medium
Sources
4

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-2017-18059 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
3Source 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
n/an/an/aListed
Weakness

CWE details

No CWE listed

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