Kernel memory corruption via tracing basename collisions
Published Nov 2, 2026 · Updated Nov 2, 2026
Use-after-free in Linux tracing histograms allows local users to corrupt kernel memory through colliding event names. In event_hist_trigger_parse() and hist_unreg_all(), basename-only matching adjusts an unrelated synthetic event's reference count, permitting deletion while a histogram action retains its pointer. Exploitation requires write access to tracefs trigger and synthetic-event controls, including delegated tracing access, and enables kernel-memory disclosure, function-pointer hijacking, or a kernel crash.
Summary
What happened
Use-after-free in Linux tracing histograms allows local users to corrupt kernel memory through colliding event names. In event_hist_trigger_parse() and hist_unreg_all(), basename-only matching adjusts an unrelated synthetic event's reference count, permitting deletion while a histogram action retains its pointer. Exploitation requires write access to tracefs trigger and synthetic-event controls, including delegated tracing access, and enables kernel-memory disclosure, function-pointer hijacking, or a kernel crash.
The record
- CVE
- CVE-2026-99233
- Published
- Nov 2, 2026
- Updated
- Nov 2, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
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=4.17
- Affected versionversion=4b147936fa509650beaf638b331573c23ba4d609 <06e816bed499fe47f39f12044382cc5d064485fb
- Affected versionversion=4b147936fa509650beaf638b331573c23ba4d609 <23b4106e8b35823acc79e206c7745f55b9cfd78b
- Affected versionversion=4b147936fa509650beaf638b331573c23ba4d609 <381f543ed35c434d5b707369aa5dcd69ecf440af
- Affected versionversion=4b147936fa509650beaf638b331573c23ba4d609 <4472579bd1c83708b6fe623c870cdf728e947205
- Affected versionversion=4b147936fa509650beaf638b331573c23ba4d609 <5597bb8db6855fcb97a67196d227fea359bcd81c
- Affected versionversion=4b147936fa509650beaf638b331573c23ba4d609 <cf4e31d5da80fae4c9cdbe7af55b7c3ad213f0e4
What conditions does exploitation require?
What is affected?
Published CVSS scores
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
Public exploit references
No public exploit references are available in this record.
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