cve.bz

CVE-2026-99235 linux linux

7.8 highEPSS 0.1%Fix available

High (7.8) in linux linux. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: tracing: Save the event file instead of the compatible histogram create_field_var_hist() creates a histogram on the matched event to supply a field variable, and records it on the target so it can be torn down later: hist_data = find_compatible_hist(target_hist_data, file); ... /* Save the compatible histogram information */ var_hist->hist_data = hist_data; hist_data is not the histogram it creates. It is one that was already there, whose keys the new one copies. The saved pointer has a single user, unregister_field_var_hists(), which runs when the target is removed: file = hist_data->field_var_hists[i]->hist_data->event_file; find_compatible_hist() matches on keys alone, so it can pick one with no variables of its own. check_var_refs() then returns false and the user can remove it while the target still points at it: BUG: KASAN: slab-use-after-free in event_hist_trigger_free+0x2b2/0x320 Read of size 8 at addr ffff8880093b90e0 by task init/1 Freed by task 1: kfree+0x154/0x420 event_hist_trigger_free+0x1d5/0x320 event_hist_trigger_parse+0x35f3/0x69e0 trigger_process_regex+0x1a6/0x250 Save the event file instead. It is all the dereference ever wanted, and it does not go away when the user removes a trigger.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.1% (unchanged from 0.1% a week ago) estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 5.10.273
  • Linux Linux: fixed in 5.15.224
  • Linux Linux: fixed in 6.1.191
  • Linux Linux: fixed in 6.6.161
  • Linux Linux: fixed in 6.12.115
  • Linux Linux: fixed in 6.18.60
  • Linux Linux: fixed in 7.2.14
  • Linux Linux: fixed in 7.3.1
  • Debian, openSUSE, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain 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.

Badge for a README or a site

CVE-2026-99235

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-99235](https://cve.bz/cve/badge/CVE-2026-99235.svg)](https://cve.bz/cve/CVE-2026-99235)

HTML:

<a href="https://cve.bz/cve/CVE-2026-99235"><img src="https://cve.bz/cve/badge/CVE-2026-99235.svg" alt="CVE-2026-99235"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux4.17 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.273
Linux5.155.15.224
Linux6.16.1.191
Linux6.66.6.161
Linux6.126.12.115
Linux6.186.18.60
Linux7.27.2.14
Linux7.37.3.1
Linuxlater releases7.4-rc1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.192-1DEBIAN-CVE-2026-99235
Debian12linux-6.126.12.115-2~deb12u1DEBIAN-CVE-2026-99235
Debian13linux6.12.115-1DEBIAN-CVE-2026-99235
Debian14linux7.2.14-1DEBIAN-CVE-2026-99235
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-99235
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-99235
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-99235
Ubuntu22.04:LTSlinux, linux-aws, linux-gcp and 57 moreno fix listedUBUNTU-CVE-2026-99235
Ubuntu24.04:LTSlinux, linux-aws, linux-gcp and 50 moreno fix listedUBUNTU-CVE-2026-99235
Ubuntu26.04:LTSlinux, linux-aws, linux-gcp and 12 moreno fix listedUBUNTU-CVE-2026-99235
Ubuntu26.10linux, linux-aws, linux-gcp and 6 moreno fix listedUBUNTU-CVE-2026-99235
UbuntuNvidia-BlueField:22.04:LTS, Nvidia-BlueField:24.04:LTSlinux-bluefieldno fix listedUBUNTU-CVE-2026-99235
UbuntuPro:18.04:LTSlinux-aws-5.4, linux-gcp-5.4, linux-hwe-5.4 and 4 moreno fix listedUBUNTU-CVE-2026-99235
UbuntuPro:20.04:LTSlinux, linux-aws, linux-gcp and 19 moreno fix listedUBUNTU-CVE-2026-99235
UbuntuPro:FIPS-preview:22.04:LTS, Pro:FIPS-updates:20.04:LTS, Pro:FIPS-updates:22.04:LTS and 2 morelinux-fips, linux-aws-fips, linux-gcp-fips and 1 moreno fix listedUBUNTU-CVE-2026-99235
UbuntuPro:Realtime:22.04:LTSlinux-realtime, linux-realtime-6.8, linux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-99235
1 more for Ubuntu in the JSON and on Ubuntu's page.
openSUSETumbleweedkernel-source7.3.3-1.1openSUSE-SU-2026:12497-1
Azure Linux3kernel6.6.161.1-1AZL-112571
Alpaquita23linux-lts6.1.191-r0BELL-CVE-2026-99235
Alpaquita25linux-lts6.12.115-r0BELL-CVE-2026-99235
Alpaquitastreamlinux-lts6.18.62-r0BELL-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

Red Hat rates this Moderate.

Red Hat's statement

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.

Red Hat's mitigation

--- 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)

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelAffected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelAffected
Red Hat Enterprise Linux 8kernel-rtAffected
Red Hat Enterprise Linux 9kernelAffected
Red Hat Enterprise Linux 9kernel-rtAffected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-10Affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Affected

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.

References

Check your stackJSON