# CVE-2016-0774: Memory corruption in n/a

> Local attackers can cause a system crash or gain privileges via a crafted application due to improper handling of failed copy operations in the Linux kernel pipe implementation.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Apr 2016
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-0774, GHSA-qc32-8fv3-qwvw, RHSA-2016:0494, RHSA-2016:0617, UBUNTU-CVE-2016-0774

## What is CVE-2016-0774?

CVE-2016-0774 is a medium-severity memory corruption vulnerability in Google Android, published on 27 Apr 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The (1) pipe_read and (2) pipe_write implementations in fs/pipe.c in a certain Linux kernel backport in the linux package before 3.2.73-2+deb7u3 on Debian wheezy and the kernel package before 3.10.0-229.26.2 on Red Hat Enterprise Linux (RHEL) 7.1 do not properly consider the side effects of failed __copy_to_user_inatomic and __copy_from_user_inatomic calls, which allows local users to cause a denial of service (system crash) or possibly gain privileges via a crafted application, aka an "I/O vector array overrun." NOTE: this vulnerability exists because of an incorrect fix for CVE-2015-1805.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kernel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-abi-whitelists` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-debug` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-debug-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-debug-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-debuginfo-common-i686` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-debuginfo-common-x86_64` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-doc` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-firmware` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-headers` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-573.22.1.el6 |
| `perf` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-573.22.1.el6 |
| `perf-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-573.22.1.el6 |
| `python-perf` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-573.22.1.el6 |
| `python-perf-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-abi-whitelists` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-debug` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-debug-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-debug-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-debuginfo-common-i686` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-debuginfo-common-x86_64` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-doc` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-firmware` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-headers` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-573.22.1.el6 |
| `perf` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-573.22.1.el6 |
| `perf-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-573.22.1.el6 |
| `python-perf` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-573.22.1.el6 |
| `python-perf-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-abi-whitelists` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-bootwrapper` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-debug` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-debug-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-debug-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-573.22.1.el6 |
| `kernel-debuginfo-common-i686` | Red Hat:enterprise_linux:6::server | All versions | 0:2.6.32-573.22.1.el6 |

Products: Google Android, Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2016-0774 being exploited?

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

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-0774 is a medium-severity memory corruption vulnerability in Google Android, published on 27 Apr 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-0774 in the wild and no public exploit code.

Affected product: Google Android. 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-0774/ (Markdown: https://insights.sbomify.com/CVE-2016-0774/index.md)
```

## Sources

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

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