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-99237 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-99237?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-99237?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-99237 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.16 and later |
| Product | Release line | Fixed in |
|---|---|---|
| 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 | 14 | linux | 7.2.14-1 | DEBIAN-CVE-2026-99237 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-99237 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-99237 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-99237 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 more | no fix listed | UBUNTU-CVE-2026-99237 |
| Ubuntu | 24.04:LTS | linux-riscv, linux-aws-7.0, linux-gcp-7.0 and 33 more | no fix listed | UBUNTU-CVE-2026-99237 |
| Ubuntu | 26.04:LTS | linux, linux-aws, linux-gcp and 12 more | no fix listed | UBUNTU-CVE-2026-99237 |
| Ubuntu | 26.10 | linux, linux-aws, linux-gcp and 6 more | no fix listed | UBUNTU-CVE-2026-99237 |
| Ubuntu | Pro:Realtime:24.04:LTS | linux-realtime-6.14, linux-realtime-6.17 | no fix listed | UBUNTU-CVE-2026-99237 |
| openSUSE | Tumbleweed | kernel-source | 7.3.3-1.1 | openSUSE-SU-2026:12497-1 |
| Alpaquita | stream | linux-lts | 6.18.62-r0 | BELL-CVE-2026-99237 |
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.
--- 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 serialize access to last-boot trace data in the kernel tracing subsystem by acquiring trace_types_lock during reader operations: upgrade to the fixed release, which acquire trace_types_lock in update_last_data_if_empty when handling last-boot buffers and route existing locked call sites to an unlocked helper variant, closing all 3 injection vectors (concurrent tracing_read_pipe calls, concurrent tracing_buffers_read operations, concurrent tracing_open calls with O_TRUNC). Until patched, this is only a concern on Linux systems where local users have permissions to read or open tracing filesystem files — Non-Linux operating systems are unaffected — so restrict access permissions on tracefs and debugfs interfaces so unprivileged or untrusted local accounts cannot open or read tracing files. As a compensating measure, enable KASAN to detect kernel use-after-free and double-free conditions at runtime, run SELinux in enforcing mode to block unprivileged and confined domains from opening or reading tracefs files, confine login users through SELinux user mappings to restrict access to administrative kernel tracing interfaces, isolate containerized processes using mount and user namespaces so tracefs is unmounted and inaccessible, drop administrative capabilities from untrusted processes to prevent interaction with restricted tracing interfaces, and deploy Falco or eBPF runtime security agents to detect anomalous read and open operations on tracing subsystem files. These controls limit blast radius and contain exploitation, but they do not fix the underlying missing locking race condition — 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 | Not 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 | Not 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 | Not affected | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-10 | Not affected | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-9 | Not 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-99237.