LiveActive security incident?Get immediate response
CVE Record

CVE-2016-2062: The adreno_perfcounter_query_group function in drivers/gpu/msm/adreno_perfcounter.c in the Adreno GPU drive...

The adreno_perfcounter_query_group function in drivers/gpu/msm/adreno_perfcounter.c in the Adreno GPU driver for the Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, uses an incorrect integer data type, which allows attackers to cause a denial of service (integer overflow, heap-based buffer overflow, and incorrect memory allocation) or possibly have unspecified other impact via a crafted IOCTL_KGSL_PERFCOUNTER_QUERY ioctl call.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2016-2062 affects Qualcomm Adreno GPU driver code used in Linux 3.x Android kernels for MSM devices. A malformed performance-counter ioctl can trigger incorrect allocation and buffer overflow behavior, causing denial of service and possibly other unspecified impact. The bundle does not provide a CVSS score or confirmed exploitation. Exposure is most likely on Android/MSM devices or products using the affected Linux 3.x Adreno GPU driver code. The provided affected-product metadata is incomplete and lists no precise vendor, product, version, or CPE inventory. Prioritize this for legacy Android or embedded fleets using Qualcomm MSM platforms. Business urgency is lower if no affected devices remain, but unsupported devices should be treated as residual operational risk because the bundle lacks precise version boundaries. Mitigation focus: Apply OEM or vendor updates containing the referenced Adreno driver fix.; Review the Android 2016-06-01 security bulletin for affected device guidance.; Check Qualcomm/CodeAurora advisory material for product-specific remediation details..

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-2016-2062 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.

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.