CVE-2026-80778

futex/pi: Reject cross-mm private futex owners

N/A
Published: September 4, 2026 at 03:12 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: futex/pi: Reject cross-mm private futex owners A private futex key borrows the waiter's mm without taking an mm_users reference. Nevertheless, attach_to_pi_owner() currently accepts an owner from a different address space and copies the private key into the owner's PI state. When that owner exits, exit_pi_state_list() uses the saved key to find the hash bucket and acquires a reference to the waiter's private hash. If the last user of the waiter's mm exits concurrently, futex_hash_free() frees the hash while the owner still uses its bucket and reference. Prevent this by validating in attach_to_pi_owner() that, for private futexes, the owner mm and waiter mm are the same. Perform the check with the owner's pi_lock held and after validating owner::futex::state to serialize against a concurrent PI-state exit cleanup. [ tglx: Amended comment ]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.1680367ad01d93ac781b0e1df246edaf006928002f
Vendor states this is fixed in 2b92e5562653b5293529f63b0300837d9dcedbd7 (fixed)
Vendor states this is fixed in 43b148d796aa338858792d0167cebdc12b8cb4b9 (fixed)
Vendor states this is fixed in 59b3732f95dda1fbd2234514d35f4fb6b5bb6d85 (fixed)
Vendor states this is fixed in f7fb3e07752688842cbe0b85cf0d98c2fbf76b68 (fixed)
Vendor states this is fixed in 6.16 (unaffected)
Vendor states this is fixed in 6.18.47 (unaffected)
Vendor states this is fixed in 7.1.11 (unaffected)
Vendor states this is fixed in 7.2.1 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card