CVE-2026-99236·Kernel vulnerability
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
- high
- Software
- Kernel
- Fixed in
- 5.10.273, 5.15.224, 6.1.191, 6.6.161, 6.12.115, 6.18.60, 7.2.14, 7.3.1
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.13% — higher than 2% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-99236 scores 7.8 on CVSS, so a successful attack would be serious — but at 0.13%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
How to fix this CVE
Update your Linux kernel to a patched stable release to fix an issue where incomplete event filter expressions can cause out-of-bounds memory access during perf tracepoint event configuration. Identify your current kernel version and upgrade to the corresponding fixed release: 5.10.273, 5.15.224, 6.1.191, 6.6.161, 6.12.115, 6.18.60, 7.2.14, or 7.3.1 depending on your kernel series. Most users should obtain the patched kernel through their distribution's package manager rather than compiling from mainline.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your current kernel version with: uname -r
- Step 2: Compare the version output against the fixed versions (5.10.273, 5.15.224, 6.1.191, 6.6.161, 6.12.115, 6.18.60, 7.2.14, 7.3.1); if your version is older, you are vulnerable
- Step 3: Check for perf event filter usage in your environment with: grep -r 'PERF_EVENT_IOC_SET_FILTER' /proc/*/fd/ 2>/dev/null || echo 'No active perf filters detected'
- Step 4: After patching, verify the kernel was updated with: uname -r and confirm it matches or exceeds the fixed version for your series
FAQ
What is CVE-2026-99236?
This vulnerability allows incomplete perf event filter expressions (such as expressions ending with a logical operator) to bypass validation checks and access out-of-bounds kernel memory, potentially leading to information disclosure or denial of service. The issue occurs in the Linux kernel's event filtering subsystem when malformed filter predicates are passed through the PERF_EVENT_IOC_SET_FILTER ioctl.
Is CVE-2026-99236 being actively exploited?
No, there is no evidence of active exploitation or public exploit code available for this vulnerability at this time.
What versions of Kernel are affected by CVE-2026-99236?
All kernel versions in the 5.10, 5.15, 6.1, 6.6, 6.12, 6.18, 7.2, and 7.3 series before their respective fixed releases are affected. The specific fixed versions are: 5.10.273, 5.15.224, 6.1.191, 6.6.161, 6.12.115, 6.18.60, 7.2.14, and 7.3.1.
How do I check if my server is vulnerable to CVE-2026-99236?
Run: uname -r to get your kernel version, then compare it against the fixed version list for your kernel series. If your version is older than the fixed release in your series, your system is vulnerable.
Does Defensia detect CVE-2026-99236?
Yes — Defensia's CVE advisory scanner compares installed kernel package versions against the NVD database. If Linux kernel is installed on a monitored server, CVE-2026-99236 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/1008e9e0b8280d47f1ab5e9c113f666a023a9697
- https://git.kernel.org/stable/c/15ff3cc7f2beecc3f95d66358f20ad7b057466aa
- https://git.kernel.org/stable/c/1fdc4164e488916402badddbb1f51e9380dabb91
- https://git.kernel.org/stable/c/2a98f5d4913ec081e08e1075512cb7ec313d9f72
- https://git.kernel.org/stable/c/4a1a6d35359991c5d47f4bf101cfbe1475c94093
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-99236. Free for 1 server.
Get started free