data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-80758 in the interactive tracker

CVE-2026-80758

futex: Avoid private hash use-after-free on final put

EPSS 0.2%

Published 2026-09-04 (44 days ago) by the Linux kernel CNA. Subsystem kernel/futex. Debian urgency: unimportant.

What to do, per Debian release

Debian's own status for CVE-2026-80758 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

ReleaseStatus VersionWhat this means
Debian 12bookwormnot affected6.1.190-1Nothing to do. bookworm never shipped the vulnerable code.
Debian 13trixienot affected6.12.113-1Nothing to do. trixie never shipped the vulnerable code.
Debian 14forkyfixed7.1.12-1Update the kernel and reboot. Fixed in 7.1.12-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed7.1.12-1Update 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

futex_private_hash_put() drops the reference to fph before evaluating fph->mm for wake_up_var(). futex_ref_put() enables preemption again before returning. If that put drops the final reference and the task is preempted, another task can pivot to the replacement hash and free the old hash after an RCU grace period. The first task then reads fph->mm from the freed allocation when it resumes. KASAN reports a slab-use-after-free in futex_private_hash_put(), with the read at offset 24 in a freed kmalloc-512 allocation. The allocation and free stacks point to futex_hash_allocate() and the RCU free path, respectively. Load the mm pointer while the fph reference is still held and pass the saved value to wake_up_var(). wake_up_var() uses the pointer as a waitqueue key and does not dereference the mm through it.

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.

kernel/futex/core.c

What this is
FUTEX SUBSYSTEMMAINTAINERS section matched on kernel/futex/* · linux-kernel@vger.kernel.org · Maintained

Check it on the machine

grep -w CONFIG_FUTEX /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

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
Build switch
CONFIG_FUTEX

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 kbuild Makefiles Debian linux-config packages

Signals

Published
2026-09-04 (44 days ago)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
0.17%, higher than 5.7% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
unimportantsource
Subsystem
kernel/futex

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
6.166.18.47dba60d26e9dd
6.167.1.1112cd315a7b6a
6.167.2.125408c62ed4e
6.167.31c7efabfbaf7

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2026-80758, 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.