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-99235 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-99235?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-99235?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-99235 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 | 5.10 | 5.10.273 |
| Linux | 5.15 | 5.15.224 |
| 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-99235 |
| Debian | 12 | linux-6.12 | 6.12.115-2~deb12u1 | DEBIAN-CVE-2026-99235 |
| Debian | 13 | linux | 6.12.115-1 | DEBIAN-CVE-2026-99235 |
| Debian | 14 | linux | 7.2.14-1 | DEBIAN-CVE-2026-99235 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-99235 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-99235 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-99235 |
| Ubuntu | 22.04:LTS | linux, linux-aws, linux-gcp and 57 more | no fix listed | UBUNTU-CVE-2026-99235 |
| Ubuntu | 24.04:LTS | linux, linux-aws, linux-gcp and 50 more | no fix listed | UBUNTU-CVE-2026-99235 |
| Ubuntu | 26.04:LTS | linux, linux-aws, linux-gcp and 12 more | no fix listed | UBUNTU-CVE-2026-99235 |
| Ubuntu | 26.10 | linux, linux-aws, linux-gcp and 6 more | no fix listed | UBUNTU-CVE-2026-99235 |
| Ubuntu | Nvidia-BlueField:22.04:LTS, Nvidia-BlueField:24.04:LTS | linux-bluefield | no fix listed | UBUNTU-CVE-2026-99235 |
| 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-99235 |
| Ubuntu | Pro:20.04:LTS | linux, linux-aws, linux-gcp and 19 more | no fix listed | UBUNTU-CVE-2026-99235 |
| 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-99235 |
| Ubuntu | Pro:Realtime:22.04:LTS | linux-realtime, linux-realtime-6.8, linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-99235 |
| 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-112571 |
| Alpaquita | 23 | linux-lts | 6.1.191-r0 | BELL-CVE-2026-99235 |
| Alpaquita | 25 | linux-lts | 6.12.115-r0 | BELL-CVE-2026-99235 |
| Alpaquita | stream | linux-lts | 6.18.62-r0 | BELL-CVE-2026-99235 |
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 Moderate.
A lifetime tracking error in tracing histograms leaves the target field variable histogram with a pointer to a compatible hist_data object that the user can remove first. Removing the target later dereferences the freed object in unregister_field_var_hists, producing a confirmed slab use after free read and potentially a kernel crash. For the CVSS the PR:H base case reflects that reliable triggering normally requires administrative write access to tracefs histogram trigger files. For the CVSS the PR:L paranoid case reflects deployments that delegate tracing instance or trigger management to a restricted local service or operator. The demonstrated impact is local denial of service. Slab reuse could make the stale event_file value invalid and create broader memory safety consequences, but no reliable arbitrary write or information disclosure primitive is established.
--- 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 write permissions to tracefs and event trigger configuration files to trusted administrators: upgrade to the corresponding fixed Red Hat builds, which save a direct pointer to trace_event_file instead of the compatible histogram pointer in struct field_var_hist, closing all 2 injection vectors (trace event trigger manipulation, premature deletion of a referenced compatible histogram trigger). Until patched, this is only a concern on Linux systems where local users have write permissions to configure trace event triggers — Non-Linux operating systems are unaffected — so restrict and audit write access to tracefs and event trigger control files to prevent unprivileged accounts from creating and deleting histogram triggers. As a compensating measure, enable runtime memory error detection such as KASAN or HWASan to detect slab use-after-free violations during trigger unregistration, enable KASLR to randomize kernel base addresses and hinder reliable execution redirection, enforce SMEP to prevent the kernel from executing userspace code if instruction pointers are redirected, enforce SMAP to block the kernel from accessing attacker-controlled userspace memory structures, enable Control Flow Integrity or Shadow Call Stack to validate indirect call targets within the kernel, and enable slab freelist hardening with freelist randomization and integrity checks to impede exploitation of freed heap memory. These controls limit blast radius and contain exploitation, but they do not fix the underlying slab use-after-free 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-99235.