LiveActive security incident?Get immediate response
CVE Record

CVE-2017-10998: In all Qualcomm products with Android releases from CAF using the Linux kernel, in audio_aio_ion_lookup_vad...

In all Qualcomm products with Android releases from CAF using the Linux kernel, in audio_aio_ion_lookup_vaddr, the buffer length, which is user input, ends up being used to validate if the buffer is fully within the valid region. If the buffer length is large enough then the address + length operation could overflow and produce a result far below the valid region.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This flaw affects Qualcomm-based Android builds from CAF using the Linux kernel. A user-controlled buffer length could overflow an address calculation, making a range check unreliable. The public bundle does not provide CVSS, confirmed impact, or exploitation evidence, so urgency depends on whether your device fleet includes affected Qualcomm Android CAF kernels. Exposure is most likely in Android devices or products using Qualcomm components with CAF-derived Linux kernels from the affected era. The source bundle does not identify specific OEM models, chipset families, Android versions, or CPEs. Treat this as an exposure-mapping issue unless affected, unpatched Qualcomm Android devices are present. If such devices remain in production and lack OEM updates, prioritize replacement or compensating mobile controls because the public data does not prove a safe generic workaround. Mitigation focus: Check OEM and Android security guidance for the September 2017 Android bulletin.; Apply available OEM or carrier security updates for affected Qualcomm Android devices.; Prioritize managed devices that run CAF-derived Qualcomm Android kernels..

Prepared

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-10998 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
2Source 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.