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-99233 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-99233?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-99233?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-99233 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 | 4.17 and later |
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.1 | 6.1.191 |
| Linux | 6.6 | 6.6.161 |
| 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.1.192-1 | DEBIAN-CVE-2026-99233 |
| Debian | 12 | linux-6.12 | 6.12.115-2~deb12u1 | DEBIAN-CVE-2026-99233 |
| Debian | 13 | linux | 6.12.115-1 | DEBIAN-CVE-2026-99233 |
| Debian | 14 | linux | 7.2.14-1 | DEBIAN-CVE-2026-99233 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-99233 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-99233 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-99233 |
| Ubuntu | 22.04:LTS | linux, linux-aws, linux-gcp and 57 more | no fix listed | UBUNTU-CVE-2026-99233 |
| Ubuntu | 24.04:LTS | linux, linux-aws, linux-gcp and 50 more | no fix listed | UBUNTU-CVE-2026-99233 |
| Ubuntu | 26.04:LTS | linux, linux-aws, linux-gcp and 12 more | no fix listed | UBUNTU-CVE-2026-99233 |
| Ubuntu | 26.10 | linux, linux-aws, linux-gcp and 6 more | no fix listed | UBUNTU-CVE-2026-99233 |
| Ubuntu | Nvidia-BlueField:22.04:LTS, Nvidia-BlueField:24.04:LTS | linux-bluefield | no fix listed | UBUNTU-CVE-2026-99233 |
| Ubuntu | Pro:18.04:LTS | linux-aws-5.4, linux-gcp-5.4, linux-hwe-5.4 and 4 more | no fix listed | UBUNTU-CVE-2026-99233 |
| Ubuntu | Pro:20.04:LTS | linux, linux-aws, linux-gcp and 19 more | no fix listed | UBUNTU-CVE-2026-99233 |
| Ubuntu | Pro:FIPS-preview:22.04:LTS, Pro:FIPS-updates:20.04:LTS, Pro:FIPS-updates:22.04:LTS and 2 more | linux-fips, linux-aws-fips, linux-gcp-fips and 1 more | no fix listed | UBUNTU-CVE-2026-99233 |
| Ubuntu | Pro:Realtime:22.04:LTS | linux-realtime, linux-realtime-6.8, linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-99233 |
| 1 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| openSUSE | Tumbleweed | kernel-source | 7.3.3-1.1 | openSUSE-SU-2026:12497-1 |
| Azure Linux | 3 | kernel | 6.6.161.1-1 | AZL-112565 |
| Alpaquita | 23 | linux-lts | 6.1.191-r0 | BELL-CVE-2026-99233 |
| Alpaquita | 25 | linux-lts | 6.12.115-r0 | BELL-CVE-2026-99233 |
| Alpaquita | stream | linux-lts | 6.18.62-r0 | BELL-CVE-2026-99233 |
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; Microsoft's Azure Linux vulnerability data, MIT; 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 Important because successful exploitation allows a local attacker to corrupt kernel memory and achieve full administrative takeover or system crashes without victim interaction. In default Red Hat Enterprise Linux configurations, the kernel tracing file hierarchy is restricted to root users, limiting exposure on typical production hosts. The issue primarily impacts multi-tenant setups or environments where permissions to manipulate tracing triggers have been explicitly delegated to less privileged accounts.
--- 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 local access to the kernel tracing file hierarchy (tracefs) to prevent manipulation of histogram triggers: upgrade to the corresponding fixed Red Hat builds, which introduce find_synth_event_call to verify that &se->call matches file->event_call before adjusting se->ref, closing histogram trigger manipulation on non-synthetic trace events matching synthetic event names. Until patched, this is only a concern on Linux systems where local users or delegated accounts have access to the kernel tracing interface — non-Linux platforms are unaffected — so restrict and audit permissions on the kernel tracing interface (tracefs) so unprivileged or untrusted users cannot register or remove histogram triggers. As a compensating measure, deploy runtime memory error detection such as KASAN to detect slab use-after-free conditions at runtime, enable SLAB freelist hardening including randomization and pointer integrity validation to impede heap grooming, enforce SELinux policies to restrict unauthorized processes from accessing tracefs and manipulating histogram triggers, drop administrative capabilities in unprivileged sandboxes and containers to prevent access to kernel tracing interfaces, enable kernel address space layout randomization to hinder predictable execution redirection following memory corruption, and enforce supervisor mode execution prevention to block execution of userspace payloads during kernel execution hijacking. These controls limit blast radius and contain exploitation, but they do not fix the underlying use-after-free reference counting 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 | Affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Affected | |
| Red Hat Enterprise Linux 9 | kernel | Affected | |
| Red Hat Enterprise Linux 9 | kernel-rt | Affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | 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-99233.