CVE-2026-99604

Description

A flaw was found in the Linux kernel's etnaviv graphics driver. This issue can result in memory corruption or a Denial of Service (DoS) when multiple applications share the graphics processing unit (GPU). Due to improper cache flushing at the completion of a graphics task on certain hardware, residual data can persist in the cache. A local user can trigger this condition by submitting graphics jobs, causing unflushed data to be written into the memory space of another process and leading to device faults or system resets.

Statement

This vulnerability is rated as Moderate severity because exploitation requires local access and is constrained to systems utilizing specific Vivante GPU hardware, limiting the blast radius. Typical Red Hat Enterprise Linux server and cloud environments do not deploy these embedded graphics processing units, substantially reducing overall exposure. On affected platforms, executing concurrent graphical workloads can leave stale cache entries across contexts, causing localized memory corruption or system crashes.

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 Score6.1N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactLowN/AN/A
Availability ImpactHighN/AN/A

Vector

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

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory; Execute Unauthorized Code or Commands

Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.

Other

Technical Impact: Unexpected State

Subsequent write operations can produce undefined or unexpected results.

Frequently Asked Questions

Want to get errata notifications? Sign up here.