# CVE-2016-2062: Integer overflow in n/a

> Attackers can cause denial of service or potential code execution via integer overflow in the Adreno GPU driver using a crafted ioctl call.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 May 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-x9c4-x5m6-x5h9

## What is CVE-2016-2062?

CVE-2016-2062 is a high-severity vulnerability in Linux kernel, published on 5 May 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2016-2062?

It affects 3 products.


Products: Google Nexus 5x Firmware, Google Nexus 6p Firmware, Linux kernel.

## How do I fix CVE-2016-2062?

No fix has been published for CVE-2016-2062 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-2062 being exploited?

There is no known exploitation of CVE-2016-2062 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-2062 and fix it if it is affected.

What it is: CVE-2016-2062 is a high-severity vulnerability in Linux kernel, published on 5 May 2016. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-2062 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-2062/ (Markdown: https://insights.sbomify.com/CVE-2016-2062/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-2062
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-2062
- OSV: https://osv.dev/vulnerability/CVE-2016-2062

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-2062/
Summaries are generated and may contain mistakes; the official description above is the record.