CVE-2026-99169

Wakeup interference via recycled memory-manager futex keys

Published Oct 28, 2026 · Updated Oct 28, 2026

Incorrect futex matching in Linux allows local users to disrupt thread wakeups via reused memory-manager addresses. get_futex_key() in kernel/futex/core.c keys FUT_OFF_MMSHARED futexes by an mm_struct address, so stale requeued waiters consume wakeups intended for a new memory manager at the same address. Triggering this requires local futex operations, cross-MM requeueing, and memory-manager address reuse; the documented consequence is missed or spurious wakeups, not a demonstrated kernel crash.

CVSS severityUnavailable
Unscored
EPSS probability0.18%
Next 30 days · Nov 1, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Contact us

Summary

What happened

Incorrect futex matching in Linux allows local users to disrupt thread wakeups via reused memory-manager addresses. get_futex_key() in kernel/futex/core.c keys FUT_OFF_MMSHARED futexes by an mm_struct address, so stale requeued waiters consume wakeups intended for a new memory manager at the same address. Triggering this requires local futex operations, cross-MM requeueing, and memory-manager address reuse; the documented consequence is missed or spurious wakeups, not a demonstrated kernel crash.

The record

CVE
CVE-2026-99169
Published
Oct 28, 2026
Updated
Oct 28, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Oct 28, 2026CVE publishedPublication date reported by the CVE source.
  2. Oct 28, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=222993395ed38f3751287f4bd82ef46b3eb3a66d <2855ddc6844f527e375e78afb55ec2a5182f23b3
  2. Affected versionversion=222993395ed38f3751287f4bd82ef46b3eb3a66d <3267512ad1c2cc0c7768c5b014dc2cceb398a801
  3. Affected versionversion=222993395ed38f3751287f4bd82ef46b3eb3a66d <c17cc2027773e8e4913c5ab0fe3a489b1ed5bf81
  4. Affected versionversion=5.7

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=222993395ed38f3751287f4bd82ef46b3eb3a66d <2855ddc6844f527e375e78afb55ec2a5182f23b3; version=222993395ed38f3751287f4bd82ef46b3eb3a66d <3267512ad1c2cc0c7768c5b014dc2cceb398a801; version=222993395ed38f3751287f4bd82ef46b3eb3a66d <c17cc2027773e8e4913c5ab0fe3a489b1ed5bf81; version=5.7

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Contact us