Kernel memory-safety violation via stale named trigger
Published Sep 25, 2026 · Updated Sep 25, 2026
Use-after-free in Linux kernel tracing allows local users to cause a kernel memory-safety violation through named histogram triggers. event_hist_trigger_named_init publishes a trigger on named_triggers before shared-histogram initialization can fail, allowing cleanup to free an object that find_named_trigger later reads. Reaching the path requires privileged tracefs access and a histogram-pad allocation failure; the demonstrated consequence is a KASAN-detected stale-object read.
Summary
What happened
Use-after-free in Linux kernel tracing allows local users to cause a kernel memory-safety violation through named histogram triggers. event_hist_trigger_named_init publishes a trigger on named_triggers before shared-histogram initialization can fail, allowing cleanup to free an object that find_named_trigger later reads. Reaching the path requires privileged tracefs access and a histogram-pad allocation failure; the demonstrated consequence is a KASAN-detected stale-object read.
The record
- CVE
- CVE-2026-97919
- Published
- Sep 25, 2026
- Updated
- Sep 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 25, 2026CVE publishedPublication date reported by the CVE source.
- Sep 25, 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=6.12.34 <6.13
- Affected versionversion=6.15.3 <6.16
- Affected versionversion=6.16
- Affected versionversion=6.6.94 <6.7
- Affected versionversion=740dab2338f70d93aa8235db5a9541d846d7b21c
- Affected versionversion=7ab0fc61ce73040f89b12d76a8279995ec283541 <0fe23b8eaba0d3372c66b7b31204408da0715edc
- Affected versionversion=7ab0fc61ce73040f89b12d76a8279995ec283541 <2ffaade3611bd9501bc0b9d5d19fc75bfee7a16b
- Affected versionversion=7ab0fc61ce73040f89b12d76a8279995ec283541 <91c15cdda6033e2439f5975b938754152f3d6e38
- Affected versionversion=ac7ab38c271ba2edaeb0dc35b200ec13339776ae
- Affected versionversion=e53a8dcd36b9ebc9229450eb594ae20e0b2ae0fd
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
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.
Get started