CVE-2026-97919
Description
A flaw was found in the Linux kernel's tracing subsystem. When creating a named histogram trigger, the kernel registers the trigger before completing its setup. If initialization fails, the object is freed without being removed from the global tracking list. A local attacker can exploit this flaw to cause a Denial of Service (DoS) through a system crash or potentially memory corruption by triggering a use-after-free condition, where the kernel accesses previously released memory.
Statement
A moderate use-after-free vulnerability was found in the Linux kernel tracing subsystem, affecting the kernel component in Red Hat Enterprise Linux 10 and Red Hat In-Vehicle OS 2. When a named histogram trigger is created, event_hist_trigger_named_init() places the trigger on the global named_triggers list before taking a reference on the trigger that shares its histogram. If initialization subsequently fails, for example when a memory allocation in alloc_hist_pad() fails, the trigger object is freed without being removed from the list, and the next lookup by name dereferences the freed memory. A local attacker able to write to tracefs event trigger files, which requires appropriate privileges, could exploit this use-after-free to crash the kernel and cause a denial of service; memory corruption may also be possible. Red Hat scored this flaw MODERATE with a CVSS 3.1 base score of 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). Red Hat Enterprise Linux 6, 7, 8, and 9, Red Hat Enterprise Linux 10.0.z, and Red Hat OpenShift 4 are not affected because the vulnerable code is not present in those kernels.
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.
