CVE-2026-99234: Linux kernel · tracing: Unregister field variable histograms when the command fails
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f21351d1c4cdcc6a68f03636a407c2af1a5e1e10 : update Linux kernel when convenient.
Data as of 2 Nov 2026, 16:31 UTC
Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in f21351d1c4cdcc6a68f03636a407c2af1a5e1e10, dba0f492703956801149cc70b39d2650a37995c3, d0090baf02dd08f6e909f36f0ad54a4e80f5e79b +5
Exploitation evidence
Disclosed: evidence found.
CVE published 2 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 2 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available and has been applied in specific Linux kernel commits identified by their hashes. Users should update to a Linux kernel version that includes these fixes to ensure proper cleanup of tracing histogram triggers on command failures. No additional mitigation steps are indicated.
Description
CVE-2026-99234 is a vulnerability in the Linux kernel tracing subsystem where field variable histograms are not properly unregistered when a command fails. This can leave histogram triggers active and counting even though their associated data structures have been freed, potentially causing resource leaks or inconsistent tracing behavior. The issue occurs due to incomplete cleanup in error paths during command parsing and histogram trigger creation.
References
- git.kernel.org/stable/c/f21351d1c4cdcc6a68f03636a407c2af1a5e1e10 (opens in a new tab)
- git.kernel.org/stable/c/dba0f492703956801149cc70b39d2650a37995c3 (opens in a new tab)
- git.kernel.org/stable/c/a3d7ffd2409700748a495b645948fef48199206e (opens in a new tab)
- git.kernel.org/stable/c/aae0ccd7326eef78dcdefffef3d1253e6f0615ca (opens in a new tab)
- git.kernel.org/stable/c/8482ec5b65f606d5bbcec518e0afc69ad65ca414 (opens in a new tab)
- git.kernel.org/stable/c/431959fc76456cbba539279fe8967aa9391e6f23 (opens in a new tab)
- git.kernel.org/stable/c/5afb9317e2eeb1c7021a82995ce244fda5a4bd4f (opens in a new tab)
- git.kernel.org/stable/c/d0090baf02dd08f6e909f36f0ad54a4e80f5e79b (opens in a new tab)