CVE-2026-89994

Description

A flaw was found in the Linux kernel's dmaengine: fsl-edma component. This vulnerability allows a local attacker to trigger a system crash, leading to a Denial of Service (DoS). The flaw occurs because the fsl edma tracing events store a pointer in a ringbuffer that can become invalid before being dereferenced during log output. An attacker can exploit this by injecting specific events.

Statement

The fsl edma trace event stores a pointer to struct fsl_edma_engine in the ring buffer and dereferences it later while formatting the trace output. The referenced engine object may already be freed or otherwise invalid at that time, resulting in a use after free read or a NULL pointer dereference and a kernel crash. Event injection provides a direct local trigger and avoids the need to win a narrow race window. For the CVSS the PR:L in the paranoid score represents systems where tracefs or event injection access is delegated to a restricted service account, container root, or another partially privileged local user. The typical configuration requires administrative tracing privileges and is represented by PR:H in the base score. The issue is not network reachable. Impact is at least local denial of service. Limited confidentiality impact is plausible if stale or reused object data affects the printed offset, but no write primitive or supported privilege escalation path is visible.

Mitigation

Mitigation for this issue is either not available or the currently available options don't 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 HatNVDcve.org
Base Score5.5N/A7.8
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.