Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-99169futex: Fix mm reuse handling for FUT_OFF_MMSHARED

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

Timeline

  1. ID reserved

    By Linux

  2. · 33 days later

    Published

  3. · 2 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (20 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 222993395ed38f3751287f4bd82ef46b3eb3a66d – < 096b5d4b80d19b1f7bf8e63fae0d0a32dbb6e1a2
    • affected 222993395ed38f3751287f4bd82ef46b3eb3a66d – < a7aa4ce1b56a688fe4da75430ec7bf9fe3311807
    • affected 222993395ed38f3751287f4bd82ef46b3eb3a66d – < f470b76584b5e32d9f9436ef78fb899914116d75
    • affected 222993395ed38f3751287f4bd82ef46b3eb3a66d – < 0c133ed51700036796318f038dde813976bf1227
    • affected 222993395ed38f3751287f4bd82ef46b3eb3a66d – < 16cc0fee39dffd9994b7bea676a886ed52206754
    • affected 222993395ed38f3751287f4bd82ef46b3eb3a66d – < c17cc2027773e8e4913c5ab0fe3a489b1ed5bf81
    • affected 222993395ed38f3751287f4bd82ef46b3eb3a66d – < 2855ddc6844f527e375e78afb55ec2a5182f23b3
    • affected 222993395ed38f3751287f4bd82ef46b3eb3a66d – < 3267512ad1c2cc0c7768c5b014dc2cceb398a801
  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.161 – ≤ 6.6.*
    • unaffected 6.12.115 – ≤ 6.12.*
    • unaffected 6.18.59 – ≤ 6.18.*
    • unaffected 7.2.13 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99169 badge
[![CVE-2026-99169](https://cveledger.app/badge/CVE-2026-99169.svg)](https://cveledger.app/cve/CVE-2026-99169)

Record last updated .