CVE-2026-97918
Description
A flaw was found in the Linux kernel's tracing subsystem. When enabling a histogram event trigger fails, improper registration cleanup can leave an already freed trigger referenced on an internal tracking list. A local attacker with permission to configure event tracing could exploit this flaw to cause a use-after-free condition, leading to a system crash and Denial of Service (DoS) or potential privilege escalation.
Statement
A use-after-free flaw was found in the Linux kernel's tracing subsystem histogram trigger implementation (kernel/trace/trace_events_hist.c), which Red Hat rates as Moderate impact. When enabling a histogram event trigger fails, the error path removes the trigger from the per-file trigger list before the normal unregistration processing runs, so the cleanup code cannot find it and skips removing its entry from the global named_triggers list; the trigger is then freed while still referenced there. Subsequent trigger operations, such as find_named_trigger(), can dereference that freed memory (KASAN reports a slab-use-after-free read), most likely crashing the kernel and causing a denial of service. Exploiting this flaw requires local access with the privileges needed to configure event tracing through tracefs, typically root or CAP_SYS_ADMIN. Because the confirmed impact is a read of freed memory by an already-privileged local user and no arbitrary memory write has been demonstrated, Red Hat assesses this as a denial-of-service issue (CVSS 3.1 score 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), lower in practical severity than the upstream description's mention of potential privilege escalation. Red Hat Enterprise Linux 6 and 7 are not affected because the vulnerable code is not present in those releases. For the affected Red Hat Enterprise Linux 8, 9, and 10, Red Hat In-Vehicle OS, and OpenShift Container Platform (RHEL CoreOS) streams, the fix is deferred: since only users who already hold administrative privileges on the system can trigger the flaw and the primary consequence is a kernel crash, the fix will be delivered in a future scheduled update rather than an immediate erratum. The residual risk is therefore limited to denial of service by an already-privileged local user.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory
If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.
Integrity,Confidentiality,Availability
Technical Impact: Execute Unauthorized Code or Commands
If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.