cve.bz

CVE-2026-99236 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: Reject incomplete event filter expressions A non-empty expression normally finishes in predicate_parse()'s inner loop, which resolves the pending logical operators before jumping to finalization. If the input ends after an operator, possibly followed by unary '!' tokens, the outer loop instead falls through with unresolved operator state. For example, "common_pid == 1 || common_pid == 2 &&" leaves prog[0].target equal to -1. The second pass then reads prog[-1] before the forward-jump check can reject it. Depending on adjacent slab contents, it can also copy an out-of-bounds word into a branch target that passes the forward-only check. A self-targeted perf tracepoint counting event can reach this path through PERF_EVENT_IOC_SET_FILTER. Reject the outer-loop fallthrough when a predicate has already been parsed. This ensures that non-empty expressions only reach finalization after the inner loop has resolved their operators. Keep the existing no-filter error for input that has no predicates. Add a regression test for trailing logical operators and unary negations.

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-99236 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-99236?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-99236?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-99236 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-99236

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-99236](https://cve.bz/cve/badge/CVE-2026-99236.svg)](https://cve.bz/cve/CVE-2026-99236)

HTML:

<a href="https://cve.bz/cve/CVE-2026-99236"><img src="https://cve.bz/cve/badge/CVE-2026-99236.svg" alt="CVE-2026-99236"></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-99236
Debian12linux-6.126.12.115-2~deb12u1DEBIAN-CVE-2026-99236
Debian13linux6.12.115-1DEBIAN-CVE-2026-99236
Debian14linux7.2.14-1DEBIAN-CVE-2026-99236
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-99236
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-99236
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-99236
Ubuntu22.04:LTSlinux, linux-aws, linux-gcp and 57 moreno fix listedUBUNTU-CVE-2026-99236
Ubuntu24.04:LTSlinux, linux-aws, linux-gcp and 50 moreno fix listedUBUNTU-CVE-2026-99236
Ubuntu26.04:LTSlinux, linux-aws, linux-gcp and 12 moreno fix listedUBUNTU-CVE-2026-99236
Ubuntu26.10linux, linux-aws, linux-gcp and 6 moreno fix listedUBUNTU-CVE-2026-99236
UbuntuNvidia-BlueField:22.04:LTS, Nvidia-BlueField:24.04:LTSlinux-bluefieldno fix listedUBUNTU-CVE-2026-99236
UbuntuPro:18.04:LTSlinux-aws-5.4, linux-gcp-5.4, linux-hwe-5.4 and 4 moreno fix listedUBUNTU-CVE-2026-99236
UbuntuPro:20.04:LTSlinux, linux-aws, linux-gcp and 19 moreno fix listedUBUNTU-CVE-2026-99236
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-99236
UbuntuPro:Realtime:22.04:LTSlinux-realtime, linux-realtime-6.8, linux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-99236
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-112574
Alpaquita23linux-lts6.1.191-r0BELL-CVE-2026-99236
Alpaquita25linux-lts6.12.115-r0BELL-CVE-2026-99236
Alpaquitastreamlinux-lts6.18.62-r0BELL-CVE-2026-99236

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 Important.

Red Hat's statement

This vulnerability is rated as an Important severity impact for Red Hat Enterprise Linux because unprivileged local attackers can exploit it to gain root privileges or force a kernel crash. Under default system configurations, trace event filtering can be reached by non-root accounts via the performance event subsystem without administrative capabilities. While the flaw cannot be triggered across the network, the ability of local users to corrupt kernel memory and hijack control flow warrants an Important rating rather than Moderate.

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 block unprivileged access to perf_event_open and tracing event filter ioctls to prevent incomplete expressions from reaching predicate_parse(): upgrade to the corresponding fixed Red Hat builds, which reject outer-loop fallthrough with -EINVAL when predicates have already been parsed, closing all 2 injection vectors (PERF_EVENT_IOC_SET_FILTER ioctl on self-targeted perf counting events, tracing event filter configuration interface). Until patched, this is only a concern on Linux systems where local users can invoke perf_event_open and ioctls or access trace event filters — Non-Linux platforms are unaffected — so Restrict and audit local user access to the perf_event_open subsystem and trace event filter configuration interfaces. As a compensating measure, Enable KASAN or HWASan runtime memory error detection to detect out-of-bounds reads in kernel slab memory, Enable Supervisor Mode Execution Prevention to prevent execution of userspace payload code during privilege escalation, Enforce Control Flow Integrity or Shadow Call Stack to prevent unauthorized redirection via corrupted branch targets, Enable kernel memory zero-initialization via init_on_alloc to mitigate reuse of stale slab data in branch targets, Maintain SELinux in enforcing mode to restrict access to tracing interfaces and confine privilege escalation blast radius, and Map local users to confined SELinux domains to limit access to tracing interfaces and post-escalation capabilities. These controls limit blast radius and contain exploitation, but they do not fix the underlying incomplete filter expression out-of-bounds read defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-601 Kernel-Level Syscall Filtering (seccomp) (high)

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-99236.

References

Check your stackJSON