# CVE-2026-99143: tracing: Keep the predicate limit separate from program capacity


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** AZL-111272, BELL-CVE-2026-99143, DEBIAN-CVE-2026-99143, GHSA-wrcg-q86c-34hw, UBUNTU-CVE-2026-99143

## What is CVE-2026-99143?

CVE-2026-99143 is a vulnerability in Linux, published on 28 Oct 2026. 

### Official description

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.

## Which versions are affected by CVE-2026-99143?


## How do I fix CVE-2026-99143?

Upgrade to a fixed version.

## Is CVE-2026-99143 being exploited?

There is no known exploitation of CVE-2026-99143 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-99143 and fix it if it is affected.

What it is: CVE-2026-99143 is a vulnerability in Linux, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99143 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-99143/ (Markdown: https://insights.sbomify.com/CVE-2026-99143/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-99143
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99143
- OSV: https://osv.dev/vulnerability/CVE-2026-99143

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-99143/
Summaries are generated and may contain mistakes; the official description above is the record.