VulnerabilityPublished 28 Oct 2026

CVE-2026-99143: Linux kernel · tracing: Keep the predicate limit separate from program capacity

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in 2058a1fe791bb30fd6e4875a7ada3237076c8541 : update Linux kernel when convenient.

Data as of 28 Oct 2026, 10:58 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Patch: Available – fixed in 2058a1fe791bb30fd6e4875a7ada3237076c8541, 803aa6fc2dbea25ab9d3ed19eca1c96d0ab17445, 68ecc9510bb82dd78585c02bd5357f34ee16b153

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to 2058a1fe791bb30fd6e4875a7ada3237076c8541, 803aa6fc2dbea25ab9d3ed19eca1c96d0ab17445 or 68ecc9510bb82dd78585c02bd5357f34ee16b153.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 39f7c41c908bc82947ce47cdd021520ff486c53f, < 2058a1fe791bb30fd6e4875a7ada3237076c8541	Fixed in 2058a1fe791bb30fd6e4875a7ada3237076c8541
LinuxLinux	Affected ≥ 39f7c41c908bc82947ce47cdd021520ff486c53f, < 803aa6fc2dbea25ab9d3ed19eca1c96d0ab17445	Fixed in 803aa6fc2dbea25ab9d3ed19eca1c96d0ab17445
LinuxLinux	Affected ≥ 39f7c41c908bc82947ce47cdd021520ff486c53f, < 68ecc9510bb82dd78585c02bd5357f34ee16b153	Fixed in 68ecc9510bb82dd78585c02bd5357f34ee16b153
LinuxLinux	Affected =6.6	Fixed in–

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.

References

Community reviews

Loading reviews…