Skip to main content
No exploitation reportedAwaiting NVD analysis

CVE-2026-99236

tracing: Reject incomplete event filter expressions

No exploitation reported by the sources we read.

  • Published2026-11-02

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2026-11-0216:06CVE publishedCNA

Observed activity

isMalicious corpus · updated 2026-11-02 15:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-99236?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-99236?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

Products declared by the CNA

As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written. NVD lists no product for this CVE yet: this is the only product data so far.

  • Linuxother versions: not affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • ≥ 80765597bc587feae8dbc8ce97a0f32e12a6e625, < 4a1a6d35359991c5d47f4bf101cfbe1475c94093fixed in 4a1a6d35359991c5d47f4bf101cfbe1475c94093git
    • ≥ 80765597bc587feae8dbc8ce97a0f32e12a6e625, < 2a98f5d4913ec081e08e1075512cb7ec313d9f72fixed in 2a98f5d4913ec081e08e1075512cb7ec313d9f72git
    • ≥ 80765597bc587feae8dbc8ce97a0f32e12a6e625, < 15ff3cc7f2beecc3f95d66358f20ad7b057466aafixed in 15ff3cc7f2beecc3f95d66358f20ad7b057466aagit
    • ≥ 80765597bc587feae8dbc8ce97a0f32e12a6e625, < b205ff58e02922ac324f931cf9eb238a3acdb048fixed in b205ff58e02922ac324f931cf9eb238a3acdb048git
    • ≥ 80765597bc587feae8dbc8ce97a0f32e12a6e625, < 5a999b5a16530898f0dbe5f8c50fd45ea72e110bfixed in 5a999b5a16530898f0dbe5f8c50fd45ea72e110bgit
    • ≥ 80765597bc587feae8dbc8ce97a0f32e12a6e625, < 1008e9e0b8280d47f1ab5e9c113f666a023a9697fixed in 1008e9e0b8280d47f1ab5e9c113f666a023a9697git
    • ≥ 80765597bc587feae8dbc8ce97a0f32e12a6e625, < 64993d970dde2a2da353e9e99595a4fa88ec27d9fixed in 64993d970dde2a2da353e9e99595a4fa88ec27d9git
    • ≥ 80765597bc587feae8dbc8ce97a0f32e12a6e625, < 5bcdf3c18c3471122ee9652b0e2f5cdb718d9a46fixed in 5bcdf3c18c3471122ee9652b0e2f5cdb718d9a46git
  • Linuxother versions: affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • = 4.17no fix stated

    Not affected < 4.17 · ≥ 5.10.273, ≤ 5.10.* · ≥ 5.15.224, ≤ 5.15.* · ≥ 6.1.191, ≤ 6.1.* · ≥ 6.6.161, ≤ 6.6.* · ≥ 6.12.115, ≤ 6.12.* · ≥ 6.18.60, ≤ 6.18.*

    2 more version lines in the CVE record.

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-02

Neither OSV.dev nor the vendor advisories we read list affected versions for CVE-2026-99236 yet.

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE record2026-11-02
  • CNACVSS 3.17.82026-11-02

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2026-11-02

Frequently asked questions

What is CVE-2026-99236?

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.

Is CVE-2026-99236 actively exploited?

Active exploitation of CVE-2026-99236 has not been confirmed.

What is the CVSS score for CVE-2026-99236?

CVE-2026-99236 has a CVSS v3 base score of 7.8 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Running Linux kernel? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record