In the Linux kernel, the following vulnerability has been resolved: tracing: Fix use-after-free with same-name named triggers When two hist triggers… (CVE-2026-89746)
A use-after-free vulnerability in the Linux kernel tracing subsystem was fixed. The issue occurs when two histogram triggers with the same name are registered on different events, leading to a dangling pointer and kernel panic when a later trigger accesses freed memory. This can be triggered from userspace by writing specific hist triggers to tracefs, causing a kernel panic due to a slab-use-after-free error.
AI Analysis
Technical Summary
The vulnerability involves the Linux kernel tracing subsystem's handling of histogram triggers with identical names on different events. When two hist triggers share the same name, the second reuses the first's named_data, but the freeing of the second's hist_data does not remove its entry from the hist_vars list, leaving a dangling pointer. Subsequent access to this freed memory by a later hist trigger causes a use-after-free condition, leading to kernel panic. The flaw is reproducible from userspace by writing three specific hist triggers to tracefs. The fix removes the hist_data from the hist_vars list and releases the trace_array reference before freeing hist_data in the named-data branch of hist_register_trigger().
Potential Impact
Exploitation of this vulnerability causes a kernel panic, resulting in a denial of service by crashing the system. The use-after-free condition can be triggered from userspace, making it possible for local users to cause system instability or crashes.
Mitigation Recommendations
A fix has been implemented that properly removes the freed hist_data from the hist_vars list and releases associated references before freeing memory. Users should apply the official kernel patch that addresses this issue. Since the vulnerability affects the Linux kernel, remediation involves updating to a fixed kernel version once available. Patch status is not yet confirmed in the provided data; check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: tracing: Fix use-after-free with same-name named triggers When two hist triggers… (CVE-2026-89746)
Description
A use-after-free vulnerability in the Linux kernel tracing subsystem was fixed. The issue occurs when two histogram triggers with the same name are registered on different events, leading to a dangling pointer and kernel panic when a later trigger accesses freed memory. This can be triggered from userspace by writing specific hist triggers to tracefs, causing a kernel panic due to a slab-use-after-free error.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability involves the Linux kernel tracing subsystem's handling of histogram triggers with identical names on different events. When two hist triggers share the same name, the second reuses the first's named_data, but the freeing of the second's hist_data does not remove its entry from the hist_vars list, leaving a dangling pointer. Subsequent access to this freed memory by a later hist trigger causes a use-after-free condition, leading to kernel panic. The flaw is reproducible from userspace by writing three specific hist triggers to tracefs. The fix removes the hist_data from the hist_vars list and releases the trace_array reference before freeing hist_data in the named-data branch of hist_register_trigger().
Potential Impact
Exploitation of this vulnerability causes a kernel panic, resulting in a denial of service by crashing the system. The use-after-free condition can be triggered from userspace, making it possible for local users to cause system instability or crashes.
Mitigation Recommendations
A fix has been implemented that properly removes the freed hist_data from the hist_vars list and releases associated references before freeing memory. Users should apply the official kernel patch that addresses this issue. Since the vulnerability affects the Linux kernel, remediation involves updating to a fixed kernel version once available. Patch status is not yet confirmed in the provided data; check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-m56h-pfxh-qxq7
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-89746"]
Threat ID: 6aa49ff755bf5e2cf5a865b6
Added to database: 09/12/2026, 00:42:31 UTC
Last enriched: 09/12/2026, 00:47:50 UTC
Last updated: 09/12/2026, 00:47:50 UTC
Views: 1
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.