Persistent tracing activity via incomplete histogram cleanup
Published Nov 2, 2026 · Updated Nov 2, 2026
Incomplete cleanup in Linux tracing allows local users to leave histogram triggers active via a rejected histogram command. The event_hist_trigger_parse() error path frees field-variable tracking entries without unregistering the auxiliary triggers created by create_field_var_hist(). Triggering the defect requires write access to tracing controls; the demonstrated consequence is an untracked histogram that continues counting, not a demonstrated crash or privilege escalation.
Summary
What happened
Incomplete cleanup in Linux tracing allows local users to leave histogram triggers active via a rejected histogram command. The event_hist_trigger_parse() error path frees field-variable tracking entries without unregistering the auxiliary triggers created by create_field_var_hist(). Triggering the defect requires write access to tracing controls; the demonstrated consequence is an untracked histogram that continues counting, not a demonstrated crash or privilege escalation.
The record
- CVE
- CVE-2026-99234
- Published
- Nov 2, 2026
- Updated
- Nov 2, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 2, 2026CVE publishedPublication date reported by the CVE source.
- Nov 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=02205a6752f223779a1b0e9e8ffacbea6e717851 <431959fc76456cbba539279fe8967aa9391e6f23
- Affected versionversion=02205a6752f223779a1b0e9e8ffacbea6e717851 <5afb9317e2eeb1c7021a82995ce244fda5a4bd4f
- Affected versionversion=02205a6752f223779a1b0e9e8ffacbea6e717851 <8482ec5b65f606d5bbcec518e0afc69ad65ca414
- Affected versionversion=02205a6752f223779a1b0e9e8ffacbea6e717851 <a3d7ffd2409700748a495b645948fef48199206e
- Affected versionversion=02205a6752f223779a1b0e9e8ffacbea6e717851 <aae0ccd7326eef78dcdefffef3d1253e6f0615ca
- Affected versionversion=02205a6752f223779a1b0e9e8ffacbea6e717851 <d0090baf02dd08f6e909f36f0ad54a4e80f5e79b
- Affected versionversion=02205a6752f223779a1b0e9e8ffacbea6e717851 <dba0f492703956801149cc70b39d2650a37995c3
- Affected versionversion=02205a6752f223779a1b0e9e8ffacbea6e717851 <f21351d1c4cdcc6a68f03636a407c2af1a5e1e10
- Affected versionversion=4.17
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
- Upstream histogram error-path reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us