CVE-2026-99169 json
futex: Fix mm reuse handling for FUT_OFF_MMSHARED
published 15d ago modified 12d ago also EUVD-2026-111921
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
futex: Fix mm reuse handling for FUT_OFF_MMSHARED
A FUT_OFF_MMSHARED futex is a shared futex that refers to an MM. It is possible for a process to wait on a shared futex with a different MM because a FUT_OFF_INODE waiter can be requeued onto a FUT_OFF_MMSHARED futex by another process. This can cause FUT_OFF_MMSHARED waiters on a freed MM to consume wakeups intended for a newly allocated MM at the same address.
Fix it by keying FUT_OFF_MMSHARED using a unique 64-bit per-MM ID. Leave private futexes as before to avoid influencing the performance of the hotpath.
(Multi-threaded processes typically implicitly use FUT_OFF_MMSHARED by setting clear_child_tid such that it points into anonymous memory, which causes mm_release() in a multi-threaded mm to perform FUTEX_WAKE.)
Patch / fix
- Linux Linux 7.3
- linux Debian 13 6.12.115-2
- linux Debian 14 7.2.13-1
debian advisories DEBIAN-CVE-2026-99169
- linux Ubuntu 26.10 7.3.0-10.10
- linux-aws Ubuntu 26.10 7.3.0-1004.4
- linux-gcp Ubuntu 26.10 7.3.0-1004.4
- linux-raspi Ubuntu 26.10 7.3.0-1004.4
- linux-riscv Ubuntu 26.10 7.3.0-10.10.1
- linux-oracle Ubuntu 26.10 7.3.0-1004.4
- linux-realtime Ubuntu 26.10 7.3.0-10.10.1
ubuntu advisories UBUNTU-CVE-2026-99169
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-111317
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/096b5d4b80d19b1f7bf8e63fae0d0a32dbb6e1a2 commit
- git.kernel.org/stable/c/a7aa4ce1b56a688fe4da75430ec7bf9fe3311807 commit
- git.kernel.org/stable/c/f470b76584b5e32d9f9436ef78fb899914116d75 commit
- git.kernel.org/stable/c/0c133ed51700036796318f038dde813976bf1227 commit
- git.kernel.org/stable/c/16cc0fee39dffd9994b7bea676a886ed52206754 commit
- git.kernel.org/stable/c/c17cc2027773e8e4913c5ab0fe3a489b1ed5bf81 commit
- git.kernel.org/stable/c/2855ddc6844f527e375e78afb55ec2a5182f23b3 commit
- git.kernel.org/stable/c/3267512ad1c2cc0c7768c5b014dc2cceb398a801 commit
Is CVE-2026-99169 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-99169 updated cvss 4.7
kernel: futex: Fix mm reuse handling for FUT_OFF_MMSHARED
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/096b5d4b80d19b1f7bf8e63fae0d0a32dbb6e1a2
- git.kernel.org /stable/c/a7aa4ce1b56a688fe4da75430ec7bf9fe3311807
- git.kernel.org /stable/c/f470b76584b5e32d9f9436ef78fb899914116d75
- git.kernel.org /stable/c/0c133ed51700036796318f038dde813976bf1227
- git.kernel.org /stable/c/16cc0fee39dffd9994b7bea676a886ed52206754
- git.kernel.org /stable/c/c17cc2027773e8e4913c5ab0fe3a489b1ed5bf81
- git.kernel.org /stable/c/2855ddc6844f527e375e78afb55ec2a5182f23b3
- git.kernel.org /stable/c/3267512ad1c2cc0c7768c5b014dc2cceb398a801
Sources
- CVE List CVE-2026-99169
- NVD CVE-2026-99169
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.