CVSS 3.1
7.8 highCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HHigh (7.8) in linux linux. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExplain CVE-2026-99227 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-99227?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-99227?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-99227 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | 6.7 and later |
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.12 | 6.12.115 |
| Linux | 6.18 | 6.18.60 |
| Linux | 7.2 | 7.2.14 |
| Linux | 7.3 | 7.3.1 |
| Linux | later releases | 7.4-rc1 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | linux-6.12 | 6.12.115-2~deb12u1 | DEBIAN-CVE-2026-99227 |
| Debian | 13 | linux | 6.12.115-1 | DEBIAN-CVE-2026-99227 |
| Debian | 14 | linux | 7.2.14-1 | DEBIAN-CVE-2026-99227 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-99227 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-99227 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-99227 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 40 more | no fix listed | UBUNTU-CVE-2026-99227 |
| Ubuntu | 24.04:LTS | linux, linux-aws, linux-gcp and 50 more | no fix listed | UBUNTU-CVE-2026-99227 |
| Ubuntu | 26.04:LTS | linux, linux-aws, linux-gcp and 12 more | no fix listed | UBUNTU-CVE-2026-99227 |
| Ubuntu | 26.10 | linux, linux-aws, linux-gcp and 6 more | no fix listed | UBUNTU-CVE-2026-99227 |
| Ubuntu | Nvidia-BlueField:24.04:LTS | linux-bluefield | no fix listed | UBUNTU-CVE-2026-99227 |
| Ubuntu | Pro:FIPS-updates:24.04:LTS | linux-fips, linux-aws-fips, linux-gcp-fips and 1 more | no fix listed | UBUNTU-CVE-2026-99227 |
| Ubuntu | Pro:Realtime:22.04:LTS | linux-realtime-6.8 | no fix listed | UBUNTU-CVE-2026-99227 |
| Ubuntu | Pro:Realtime:24.04:LTS | linux-realtime, linux-realtime-6.14, linux-realtime-6.17 and 1 more | no fix listed | UBUNTU-CVE-2026-99227 |
| openSUSE | Tumbleweed | kernel-source | 7.3.3-1.1 | openSUSE-SU-2026:12497-1 |
| Alpaquita | 25 | linux-lts | 6.12.115-r0 | BELL-CVE-2026-99227 |
| Alpaquita | stream | linux-lts | 6.18.62-r0 | BELL-CVE-2026-99227 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.
Red Hat rates this Important.
This vulnerability is rated as an Important severity flaw because an unprivileged local user can leverage repeated asynchronous wait cancellation requests to induce memory corruption and potentially achieve local privilege escalation or crash the kernel. Although exploitation requires existing local system access, default system configurations permit unprivileged callers to interact with io_uring operations without special capabilities. Successful exploitation compromises the integrity and confidentiality of the host kernel, posing a significant risk in multi-tenant or containerized environments.
--- CME Mitigation Guidance (2026-11-04) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to restrict unprivileged user access to the io_uring subsystem to prevent asynchronous cancellation requests from reaching kernel waitid logic: upgrade to the corresponding fixed Red Hat builds, which use atomic_fetch_or to inspect the prior cancel flag and return immediately without incrementing the reference counter if the cancel flag was already set, closing repeated cancellation requests on io_uring waitid operations. Until patched, this is only a concern on Linux systems allowing unprivileged users to submit io_uring operations — Non-Linux platforms are unaffected — so restrict unprivileged local users from submitting io_uring operations or interacting with asynchronous waitid requests. As a compensating measure, enable Kernel AddressSanitizer to detect use-after-free memory access caused by io_uring double completions, enable SLAB freelist randomization and pointer integrity validation to detect heap layout manipulation during use-after-free exploitation, maintain SELinux in enforcing mode to confine processes and limit lateral movement following privilege escalation, deploy endpoint detection agents to detect post-exploitation payload deployment and privilege escalation behaviors, deploy eBPF runtime security monitoring to detect anomalous kernel activity and unauthorized privilege elevation attempts, and enforce hardware non-executable page protections to prevent execution of injected code residing in kernel heap memory. These controls limit blast radius and contain exploitation, but they do not fix the underlying reference counter wrap defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-301 SELinux (Enforcing Mode) (medium)
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Affected | |
| Red Hat Enterprise Linux 6 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Not affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 9 | kernel | Affected | |
| Red Hat Enterprise Linux 9 | kernel-rt | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-9 | Affected | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-10 | Affected | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-9 | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-99227.