CVE-2026-80775
futex: Fix race on the initial mm->futex.phash.ref allocation
Reported by linux · Published September 4, 2026
In the Linux kernel, the following vulnerability has been resolved: futex: Fix race on the initial mm->futex.phash.ref allocation futex_hash_allocate() allocates mm->futex.phash.ref without any locking. Commit d9b05321e21e ("futex: Move futex_hash_free() back to __mmput()") moved the allocation here and assumed that the process has just a single thread at this point. Commit ee9dce44362b ("futex: Drop CLONE_THREAD requirement for private default hash alloc") widened need_futex_hash_allocate_default() to cover any CLONE_VM clone, but left out vfork because the parent is suspended and cannot race. That no longer holds once vfork is nested. If a vfork child calls vfork again and is then killed with SIGKILL, the parent is released from its vfork wait and runs concurrently with the grandchild in the same mm. Neither of them went through futex_hash_allocate_default(). When both call prctl(PR_FUTEX_HASH, PR_FUTEX_HASH_SET_SLOTS) at the same time, each one sees mm->futex.phash.ref as NULL and stores its own percpu counter. Only the last store survives. The counter stored first is no longer reachable from the mm, so the references on it are not seen by __futex_ref_atomic_end(). A private hash that still has references is then considered dead and freed, and a task that still holds one of its buckets writes into freed memory in futex_q_lock(). Store the counter once with cmpxchg() and let the loser free_percpu() its own. The initial reference has to be taken before the store, otherwise another task can install a private hash while the counter is still 0.
EPSS 0.19% · 8.2th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel-zfcpdump-devel | errata.rockylinux.org | 5.14.0-687.54.1.el9 |
| kernel-zfcpdump-modules | errata.rockylinux.org | 5.14.0-687.54.1.el9 |
| python3-perf-debuginfo | errata.rockylinux.org | 5.14.0-687.54.1.el9 |
| kernel-debuginfo-common-x86_64 | errata.rockylinux.org | 5.14.0-687.54.1.el9 |
| kernel-debug-modules-core | errata.rockylinux.org | 5.14.0-687.54.1.el9 |
| kernel-64k-debug-devel | errata.rockylinux.org | 5.14.0-687.54.1.el9 |
| kernel-debug-devel | errata.rockylinux.org | 5.14.0-687.54.1.el9 |
| kernel-rt-debuginfo | errata.rockylinux.org | 5.14.0-687.54.1.el9 |
| kernel-zfcpdump-debuginfo | errata.rockylinux.org | 5.14.0-687.54.1.el9 |
| rtla | errata.rockylinux.org | 5.14.0-687.54.1.el9 |
| libperf | errata.rockylinux.org | 5.14.0-687.54.1.el9 |
| kernel-64k-modules-extra | errata.rockylinux.org | 5.14.0-687.54.1.el9 |
4 more packages have a fixed version. See every fix in Lookup.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | d9b05321e21e4b218de4ce8a590bf375f58b6346, d9b05321e21e4b218de4ce8a590bf375f58b6346, d9b05321e21e4b218de4ce8a590bf375f58b6346 |
| Linux | Linux | 6.17, 0, 6.18.47 |
| Linux | Linux | *, *, 7.3 |
| amazon:2023 | perf6.18 | 0 |
| linux | linux_kernel | 6.17, 6.17, 6.17 |
| amazon:2023 | kernel6.18 | 0 |
| amazon:2023 | kernel-livepatch-6.18.48-107.148 | 0 |
| amazon:2023 | kernel6.18-modules-extra-common | 0 |
| amazon:2023 | kernel6.18-devel | 0 |
| amazon:2023 | bpftool6.18 | 0 |
| amazon:2023 | kernel6.18-headers | 0 |
| amazon:2023 | kernel6.18-modules-extra | 0 |
| amazon:2023 | python3-perf6.18 | 0 |
| amazon:2023 | kernel6.18-tools | 0 |
| amazon:2023 | kernel6.18-tools-devel | 0 |
| amazon:2023 | microvm-kernel6.18 | 0 |
Timeline
- Sep 4, 2026 Coalition ESS Score
- Sep 4, 2026 CVE Published
- Sep 5, 2026 EPSS Score (12 in total, the first dated here)
- Oct 2, 2026 Distribution Patch (2 in total, the first dated here)
- Oct 2, 2026 Security Advisory (2 in total, the first dated here)
- Oct 19, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-80775
vulnetix vdb fixes CVE-2026-80775
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-80775/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart