Kernel fault via dangling dynamic-event fields
Published Sep 25, 2026 · Updated Sep 25, 2026
Use-after-free in Linux tracing probes allows local users with tracing access to trigger an invalid kernel-memory read through a probe filter. traceprobe_define_arg_fields() passes probe-owned name and type strings to trace_define_field(), which stores their pointers without copying; removing the first of several probes frees those strings while a sibling keeps the event and its field list alive. Writing a filter after that removal dereferences the dangling field pointer, producing a repeatable KASAN kernel fault; reachability requires the ability to modify dynamic tracing events.
Summary
What happened
Use-after-free in Linux tracing probes allows local users with tracing access to trigger an invalid kernel-memory read through a probe filter. traceprobe_define_arg_fields() passes probe-owned name and type strings to trace_define_field(), which stores their pointers without copying; removing the first of several probes frees those strings while a sibling keeps the event and its field list alive. Writing a filter after that removal dereferences the dangling field pointer, producing a repeatable KASAN kernel fault; reachability requires the ability to modify dynamic tracing events.
The record
- CVE
- CVE-2026-98076
- Published
- Sep 25, 2026
- Updated
- Sep 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
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=5.4
- Affected versionversion=ca89bc071d5e4e981dcc52e0ca90f4500d332e42 <178ff2e011e21fbebdf57f5d58a408fe59136d82
- Affected versionversion=ca89bc071d5e4e981dcc52e0ca90f4500d332e42 <411c9080a776577664531b4f7d3ee53b7a747ba8
- Affected versionversion=ca89bc071d5e4e981dcc52e0ca90f4500d332e42 <68ae584169c7a41fc9bc4677c1d368983cf44b21
- Affected versionversion=ca89bc071d5e4e981dcc52e0ca90f4500d332e42 <86b7a239ec6b14a7544200ede85474c6f5526049
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 multiple-probe tracing 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.
Get started