CVE-2026-99227

Kernel memory corruption via cancellation reference wrap

Published Nov 2, 2026 · Updated Nov 2, 2026

Use-after-free in Linux io_uring waitid allows local users to corrupt kernel memory through repeated request cancellation. In __io_waitid_cancel(), failed cancellation attempts retain reference increments, wrapping the 31-bit counter and allowing a request to complete twice. Access to io_uring and an outstanding child-wait request are required; double completion causes kernel hangs or crashes.

CVSS severity7.8
High
EPSS probability0.12%
Next 30 days · Nov 22, 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

Use-after-free in Linux io_uring waitid allows local users to corrupt kernel memory through repeated request cancellation. In __io_waitid_cancel(), failed cancellation attempts retain reference increments, wrapping the 31-bit counter and allowing a request to complete twice. Access to io_uring and an outstanding child-wait request are required; double completion causes kernel hangs or crashes.

The record

CVE
CVE-2026-99227
Published
Nov 2, 2026
Updated
Nov 2, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1068
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Nov 2, 2026CVE publishedPublication date reported by the CVE source.
  2. Nov 2, 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=6.7
  2. Affected versionversion=f31ecf671ddc498f20219453395794ff2383e06b <20b67288574c7c3df6b8ea7ed3b7af90a868006f
  3. Affected versionversion=f31ecf671ddc498f20219453395794ff2383e06b <22fb4a4518e305164c7f203608287564de292f34
  4. Affected versionversion=f31ecf671ddc498f20219453395794ff2383e06b <5bfeee1774791602a0d53eb717f00f172127a017
  5. Affected versionversion=f31ecf671ddc498f20219453395794ff2383e06b <857aa2012b91cad6fdef54a4b6c632d9d0b6e64f

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=6.7; version=f31ecf671ddc498f20219453395794ff2383e06b <20b67288574c7c3df6b8ea7ed3b7af90a868006f; version=f31ecf671ddc498f20219453395794ff2383e06b <22fb4a4518e305164c7f203608287564de292f34; version=f31ecf671ddc498f20219453395794ff2383e06b <5bfeee1774791602a0d53eb717f00f172127a017; version=f31ecf671ddc498f20219453395794ff2383e06b <857aa2012b91cad6fdef54a4b6c632d9d0b6e64f

Published CVSS scores

7.8LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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

T1068Exploitation for Privilege Escalation

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