Strix
73.2K

CVE-2026-99169

UnknownEPSS 0.17%

Last modified

CVE-2026-99169 is a vulnerability of currently unknown severity. 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.). EPSS estimates a 0.17% chance of exploitation in the next 30 days.

Description

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.)

Metrics

EPSS Probability
0.17%

6.6th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 222993395ed38f3751287f4bd82ef46b3eb3a66d, < 096b5d4b80d19b1f7bf8e63fae0d0a32dbb6e1a2; >= 222993395ed38f3751287f4bd82ef46b3eb3a66d, < a7aa4ce1b56a688fe4da75430ec7bf9fe3311807; >= 222993395ed38f3751287f4bd82ef46b3eb3a66d, < f470b76584b5e32d9f9436ef78fb899914116d75; >= 222993395ed38f3751287f4bd82ef46b3eb3a66d, < 0c133ed51700036796318f038dde813976bf1227; >= 222993395ed38f3751287f4bd82ef46b3eb3a66d, < 16cc0fee39dffd9994b7bea676a886ed52206754; >= 222993395ed38f3751287f4bd82ef46b3eb3a66d, < c17cc2027773e8e4913c5ab0fe3a489b1ed5bf81; >= 222993395ed38f3751287f4bd82ef46b3eb3a66d, < 2855ddc6844f527e375e78afb55ec2a5182f23b3; >= 222993395ed38f3751287f4bd82ef46b3eb3a66d, < 3267512ad1c2cc0c7768c5b014dc2cceb398a801
LinuxLinux5.7

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-99169?
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.)
How severe is CVE-2026-99169?
Severity scoring for CVE-2026-99169 is pending analysis. The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2026-99169?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-99169?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST