Kernel code execution via incomplete filter expressions
Published Nov 2, 2026 · Updated Nov 2, 2026
Memory corruption in Linux tracing allows local users to execute kernel code through incomplete perf event filter expressions. In predicate_parse(), trailing logical operators leave a negative branch target unresolved, causing a read before the program array and propagation of an invalid target. Exploitation requires access to a self-targeted perf tracepoint counting event through PERF_EVENT_IOC_SET_FILTER; kernel reads, control-flow hijacking, and kernel crashes are documented consequences.
Summary
What happened
Memory corruption in Linux tracing allows local users to execute kernel code through incomplete perf event filter expressions. In predicate_parse(), trailing logical operators leave a negative branch target unresolved, causing a read before the program array and propagation of an invalid target. Exploitation requires access to a self-targeted perf tracepoint counting event through PERF_EVENT_IOC_SET_FILTER; kernel reads, control-flow hijacking, and kernel crashes are documented consequences.
The record
- CVE
- CVE-2026-99236
- Published
- Nov 2, 2026
- Updated
- Nov 2, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 2, 2026CVE publishedPublication date reported by the CVE source.
- Nov 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.17
- Affected versionversion=80765597bc587feae8dbc8ce97a0f32e12a6e625 <1008e9e0b8280d47f1ab5e9c113f666a023a9697
- Affected versionversion=80765597bc587feae8dbc8ce97a0f32e12a6e625 <15ff3cc7f2beecc3f95d66358f20ad7b057466aa
- Affected versionversion=80765597bc587feae8dbc8ce97a0f32e12a6e625 <2a98f5d4913ec081e08e1075512cb7ec313d9f72
- Affected versionversion=80765597bc587feae8dbc8ce97a0f32e12a6e625 <4a1a6d35359991c5d47f4bf101cfbe1475c94093
- Affected versionversion=80765597bc587feae8dbc8ce97a0f32e12a6e625 <5a999b5a16530898f0dbe5f8c50fd45ea72e110b
- Affected versionversion=80765597bc587feae8dbc8ce97a0f32e12a6e625 <5bcdf3c18c3471122ee9652b0e2f5cdb718d9a46
- Affected versionversion=80765597bc587feae8dbc8ce97a0f32e12a6e625 <64993d970dde2a2da353e9e99595a4fa88ec27d9
- Affected versionversion=80765597bc587feae8dbc8ce97a0f32e12a6e625 <b205ff58e02922ac324f931cf9eb238a3acdb048
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us