# CVE-2013-6282: Linux Kernel Improper Input Validation

> Attackers can read or modify arbitrary kernel memory via crafted applications on ARM platforms, leading to code execution and privilege escalation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 15 Sep 2022 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Nov 2013
- **Updated:** 22 Oct 2025
- **Also known as:** DEBIAN-CVE-2013-6282, GHSA-7p8v-5r94-xc7r

## What is CVE-2013-6282?

CVE-2013-6282 is a high-severity memory corruption vulnerability in Linux kernel, published on 19 Nov 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addresses, which allows attackers to read or modify the contents of arbitrary kernel memory locations via a crafted application, as exploited in the wild against Android devices in October and November 2013.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2013-6282?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2013-6282?

Apply the vendor's patch. US federal agencies must fix it by 6 Oct 2022.

## Is CVE-2013-6282 being exploited?

Yes. Attackers have exploited CVE-2013-6282 in the wild since at least 15 Sep 2022.

Public exploit code:

- CVE-2013-6282 exploit (github_poc): https://github.com/fi01/libput_user_exploit
- CVE-2013-6282 proof of concept for Android (github_poc): https://github.com/timwr/CVE-2013-6282
- Using CVE-2013-6282 to bypass Samsung kernel module authentication (github_poc): https://github.com/jeboo/bypasslkm
- CVE-2013-6282 exploit (github_poc): https://github.com/fi01/libget_user_exploit
- Android get_user/put_user Exploit (metasploit)
- Linux Kernel < 3.4.5 (Android 4.2.2/4.4 ARM) - Local Privilege Escalation (exploitdb)

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)
- [CVE-2026-46300](https://insights.sbomify.com/CVE-2026-46300/): Linux Kernel Missing Initialization of a Variable (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6282 and fix it if it is affected.

What it is: CVE-2013-6282 is a high-severity memory corruption vulnerability in Linux kernel, published on 19 Nov 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2013-6282 in the wild since at least 15 Sep 2022.

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-2013-6282/ (Markdown: https://insights.sbomify.com/CVE-2013-6282/index.md)
```

## Sources

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

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