CVE-2026-99143 json
tracing: Keep the predicate limit separate from program capacity
published 14d ago modified 11d ago also EUVD-2026-111895
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 7.3
- linux Debian 13 6.12.115-2
- linux Debian 14 7.2.13-1
debian advisories DEBIAN-CVE-2026-99143
- linux Ubuntu 26.10 7.3.0-10.10
- linux-aws Ubuntu 26.10 7.3.0-1004.4
- linux-gcp Ubuntu 26.10 7.3.0-1004.4
- linux-raspi Ubuntu 26.10 7.3.0-1004.4
- linux-riscv Ubuntu 26.10 7.3.0-10.10.1
- linux-oracle Ubuntu 26.10 7.3.0-1004.4
- linux-realtime Ubuntu 26.10 7.3.0-10.10.1
ubuntu advisories UBUNTU-CVE-2026-99143
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-111272
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/f4fcbae8b27350565026807e77c96541d9e7a349 commit
- git.kernel.org/stable/c/37049f8c56d377e46a8ef1ff93178a39a68a9c9c commit
- git.kernel.org/stable/c/2058a1fe791bb30fd6e4875a7ada3237076c8541 commit
- git.kernel.org/stable/c/68ecc9510bb82dd78585c02bd5357f34ee16b153 commit
- git.kernel.org/stable/c/803aa6fc2dbea25ab9d3ed19eca1c96d0ab17445 commit
Is CVE-2026-99143 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-99143 updated cvss 4.4
kernel: kernel: Denial of Service via out-of-bounds access in tracing predicate parsing
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 10 kernelaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/f4fcbae8b27350565026807e77c96541d9e7a349
- git.kernel.org /stable/c/37049f8c56d377e46a8ef1ff93178a39a68a9c9c
- git.kernel.org /stable/c/2058a1fe791bb30fd6e4875a7ada3237076c8541
- git.kernel.org /stable/c/68ecc9510bb82dd78585c02bd5357f34ee16b153
- git.kernel.org /stable/c/803aa6fc2dbea25ab9d3ed19eca1c96d0ab17445
Sources
- CVE List CVE-2026-99143
- NVD CVE-2026-99143
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.