Look up another CVE · open CVE-2026-80777 in the interactive tracker
CVE-2026-80777
futex/pi: Plug private futex exec() race
Published 2026-09-04 (44 days ago) by the Linux kernel CNA. Subsystem fs. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-80777 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | not affected | 6.12.113-1 | Nothing to do. trixie never shipped the vulnerable code. |
| Debian 14forky | fixed | 7.1.12-1 | Update the kernel and reboot. Fixed in 7.1.12-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.12-1 | Update the kernel and reboot. Fixed in 7.1.12-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
fs/exec.c
include/linux/futex.h
kernel/futex/core.c
kernel/futex/pi.c
- What this is
- EXEC & BINFMT API, ELFMAINTAINERS section matched on fs/exec.c · linux-mm@kvack.org · Supported
Show whether Debian builds this, per release
Debian builds this code. Every release below compiles the affected file into the kernels it ships.
- bookworm, trixie, forky, sidy
- y
- built into the kernel image on every flavour - only a patch removes it
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS Debian linux-config packages
Signals
- Published
- 2026-09-04 (44 days ago)source
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- 0.21%, higher than 10.3% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- fs
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.16 | 6.18.47 | fdf538b2e696 |
| 6.16 | 7.1.11 | 0478bc6bf197 |
| 6.16 | 7.2.1 | d7944cee62ec |
| 6.16 | 7.3 | c5f0bc9fd1ce |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2026-80777, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.