# CVE-2015-1805: Memory corruption in n/a

> Local attackers can exploit a Linux kernel pipe implementation flaw to cause a system crash or potentially escalate privileges via a crafted application.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** Yes
- **Published:** 8 Aug 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-1805, GHSA-c8vr-r7wq-hc48, RHSA-2015:1042, RHSA-2015:1120, RHSA-2015:1190, RHSA-2015:1211, UBUNTU-CVE-2015-1805

## What is CVE-2015-1805?

CVE-2015-1805 is a high-severity memory corruption vulnerability in Google Android, published on 8 Aug 2015. 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 the Linux kernel before 3.16 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."

Weakness: CWE-17

## Which versions are affected by CVE-2015-1805?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kernel` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-406.el5 |
| `kernel-PAE` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-406.el5 |
| `kernel-PAE-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-406.el5 |
| `kernel-PAE-devel` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-406.el5 |
| `kernel-debug` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-406.el5 |
| `kernel-debug-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-406.el5 |
| `kernel-debug-devel` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-406.el5 |
| `kernel-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-406.el5 |
| `kernel-debuginfo-common` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-406.el5 |
| `kernel-devel` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-406.el5 |
| `kernel-doc` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-406.el5 |
| `kernel-headers` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-406.el5 |
| `kernel-xen` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-406.el5 |
| `kernel-xen-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-406.el5 |
| `kernel-xen-devel` | Red Hat:enterprise_linux:5::client | All versions | 0:2.6.18-406.el5 |
| `kernel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-406.el5 |
| `kernel-PAE` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-406.el5 |
| `kernel-PAE-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-406.el5 |
| `kernel-PAE-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-406.el5 |
| `kernel-debug` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-406.el5 |
| `kernel-debug-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-406.el5 |
| `kernel-debug-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-406.el5 |
| `kernel-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-406.el5 |
| `kernel-debuginfo-common` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-406.el5 |
| `kernel-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-406.el5 |
| `kernel-doc` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-406.el5 |
| `kernel-headers` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-406.el5 |
| `kernel-kdump` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-406.el5 |
| `kernel-kdump-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-406.el5 |
| `kernel-kdump-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-406.el5 |
| `kernel-xen` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-406.el5 |
| `kernel-xen-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-406.el5 |
| `kernel-xen-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.6.18-406.el5 |
| `kernel` | Red Hat:rhel_aus:5.9 | All versions | 0:2.6.18-348.31.2.el5 |
| `kernel-PAE` | Red Hat:rhel_aus:5.9 | All versions | 0:2.6.18-348.31.2.el5 |
| `kernel-PAE-debuginfo` | Red Hat:rhel_aus:5.9 | All versions | 0:2.6.18-348.31.2.el5 |
| `kernel-PAE-devel` | Red Hat:rhel_aus:5.9 | All versions | 0:2.6.18-348.31.2.el5 |
| `kernel-debug` | Red Hat:rhel_aus:5.9 | All versions | 0:2.6.18-348.31.2.el5 |
| `kernel-debug-debuginfo` | Red Hat:rhel_aus:5.9 | All versions | 0:2.6.18-348.31.2.el5 |
| `kernel-debug-devel` | Red Hat:rhel_aus:5.9 | All versions | 0:2.6.18-348.31.2.el5 |

Products: Google Android, Linux kernel.

## How do I fix CVE-2015-1805?

Apply the vendor's patch.

## Is CVE-2015-1805 being exploited?

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

Public exploit code:

- CVE-2015-1805 root tool (github_poc): https://github.com/dosomder/iovyroot
- https://github.com/panyu6325/CVE-2015-1805 (github_poc): https://github.com/panyu6325/CVE-2015-1805
- AndroRAT is a capability that can be used to inject a root exploit as a silent installation to perform a malicious task on the device. This AndroRAT is designed to exploit CVE-2015-1805, a vulnerability that was discovered and made public in 2016. (github_poc): https://github.com/ireshchaminda1/Android-Privilege-Escalation-Remote-Access-Vulnerability-CVE-2015-1805
- https://github.com/FloatingGuy/cve-2015-1805 (github_poc): https://github.com/FloatingGuy/cve-2015-1805
- HP Slate 7 2800 Android 4.1.1 rooting kit using CVE-2015-1805. (github_poc): https://github.com/valentineus/hp-slate7-root-kit
- A root tool based on the [CVE-2015-1805 vulnerability](https://access.redhat.com/security/cve/cve-2015-1805)  It supports 32 and 64bit, get sys call table address via swi. (github_poc): https://github.com/mobilelinux/iovy_root_research

## 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-2015-1805 and fix it if it is affected.

What it is: CVE-2015-1805 is a high-severity memory corruption vulnerability in Google Android, published on 8 Aug 2015. 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-2015-1805 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-2015-1805/ (Markdown: https://insights.sbomify.com/CVE-2015-1805/index.md)
```

## Sources

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

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