# CVE-2014-3153: Linux Kernel Privilege Escalation

> Local attackers can gain privileges via a crafted FUTEX_REQUEUE command due to missing address validation in the Linux kernel futex implementation.

- **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:** Yes, since 25 May 2022 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jun 2014
- **Updated:** 22 Oct 2025
- **Also known as:** DEBIAN-CVE-2014-3153, GHSA-5gr7-gr2q-52gp, UBUNTU-CVE-2014-3153

## What is CVE-2014-3153?

CVE-2014-3153 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 7 Jun 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The futex_requeue function in kernel/futex.c in the Linux kernel through 3.14.5 does not ensure that calls have two different futex addresses, which allows local users to gain privileges via a crafted FUTEX_REQUEUE command that facilitates unsafe waiter modification.

## Which versions are affected by CVE-2014-3153?

It affects 9 products.


Products: Canonical Ubuntu Linux, Linux kernel, Opensuse Opensuse, Oracle Linux, Redhat Enterprise Linux Server Aus, Suse Linux Enterprise Desktop, Suse Linux Enterprise High Availability Extension, Suse Linux Enterprise Real Time Extension, Suse Linux Enterprise Server.

## How do I fix CVE-2014-3153?

Apply the vendor's patch. US federal agencies must fix it by 15 Jun 2022.

## Is CVE-2014-3153 being exploited?

Yes. Attackers have exploited CVE-2014-3153 in the wild since at least 25 May 2022.

Public exploit code:

- CVE-2014-3153 aka towelroot (github_poc): https://github.com/timwr/CVE-2014-3153
- Research of CVE-2014-3153 and its famous exploit towelroot on x86 (github_poc): https://github.com/geekben/towelroot
- Gain root privilege by exploiting CVE-2014-3153 vulnerability (github_poc): https://github.com/dangtunguyen/TowelRoot
- CVE-2014-3153 exploit (github_poc): https://github.com/android-rooting-tools/libfutex_exploit
- cve2014-3153 exploit for ubuntu x86 (github_poc): https://github.com/lieanu/CVE-2014-3153
- Exploiting CVE-2014-3153, AKA Towelroot. (github_poc): https://github.com/elongl/CVE-2014-3153

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-3153 and fix it if it is affected.

What it is: CVE-2014-3153 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 7 Jun 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2014-3153 in the wild since at least 25 May 2022.

Affected product: Canonical Ubuntu Linux. 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-2014-3153/ (Markdown: https://insights.sbomify.com/CVE-2014-3153/index.md)
```

## Sources

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

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