KernelScan.io

HIGH Introduced in 6.6

tracing Predicate Overflow

CVE-2026-99143

CVSS 7.8 / 10.0 NVD

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

KernelScan AI7.8HIGH

01

In the Linux kernel, the following vulnerability has been resolved: tracing: Keep the predicate limit separate from program capacity predicate_parse() adds two to nr_preds to reserve the terminal TRUE and FALSE entries. It also uses that increased value as the limit for parsed predicates. If the initial count is smaller than the number actually parsed, the program can fill the allocation and subsequent accesses can go past its end. Keep nr_preds as the predicate limit and use a separate value for the allocation size. This leaves space for both terminal entries and a zeroed entry when parsing stops at the limit.

02

Engine v0.9.0

Risk summary

A local attacker with access to tracefs (typically requiring CAP_SYS_ADMIN or CAP_TRACE_ADMIN) can trigger an out-of-bounds write in the kernel's trace event filter parser by supplying a crafted filter expression. This allows kernel memory corruption leading to privilege escalation, information disclosure, or denial of service. Systems exposing tracefs to unprivileged users or containers are at elevated risk.

Affectedkernel/trace/trace_events_filter.c (tracing)

Vulnerability analysis

The trace event filter parser incorrectly used a single counter for both the maximum number of predicates allowed and the allocation size for the predicate program array. When parsing a filter string, the code added two to this counter to reserve space for terminal TRUE/FALSE entries, but then used the inflated value as the parsing limit. If a filter expression contained more predicates than the original limit (but fewer than the inflated limit), the parser would write past the allocated buffer, corrupting adjacent kernel heap memory. The fix separates the predicate limit from the allocation size, ensuring the buffer is always large enough for the parsed predicates plus the required terminal entries. The vulnerability is reachable locally by any process that can write filter expressions to tracefs, which typically requires administrative capabilities but may be delegated to non-root users or containers in some deployments.

03

BranchIntroducedFixed inPatch commit
6.126.66.12.11537049f8c56d3
6.186.66.18.592058a1fe791b
6.66.66.6.161f4fcbae8b273
7.26.67.2.1368ecc9510bb8
mainline6.67.3803aa6fc2dbe

04

State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.

CIP treeState
cip/6.12Affected — no CIP fix yet (latest 6.12.114-cip34)