CVE Catalog

CVE-2026-80777

Unknown
Published: Translated: NVD NIST

Summary

In the Linux kernel's futex/pi mechanism, there is a race condition during exec() for private futexes. There is a window between setting exit_state to OK and changing the mm pointer where the mm check is incorrect, potentially leading to use-after-free. The fix sets exit_state to FUTEX_STATE_DEAD in futex_exec_release() and only sets it to FUTEX_STATE_OK after the mm switch.

Risk Assessment

The vulnerability could be exploited to gain unauthorized access to kernel memory, potentially leading to system crash or privilege escalation.

Recommendation

Urgently apply the Linux kernel patch that closes the race window, and update the system to a patched version.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS