CVE-2026-99468

Description

A flaw was found in the Linux kernel's i.MX JPEG driver. The driver fails to properly cancel pending background timeout tasks before releasing session memory when a device file is closed while an active processing job is running. A local attacker could exploit this issue to trigger a use-after-free memory error, leading to a system crash and Denial of Service (DoS) or potential privilege escalation.

Statement

This vulnerability is rated as Moderate severity for Red Hat products because exploitation requires local access to an NXP i.MX video device and precise timing during stream shutdown, limiting the blast radius to a denial of service (system crash) without remote exposure. The affected media driver is specific to NXP i.MX System-on-Chip (SoC) hardware architectures and is not utilized in standard enterprise server environments. Systems lacking this specialized hardware acceleration driver or with the corresponding module unloaded are not exposed to this flaw.

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 Score4.7N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredLowN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:L/AC:H/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

Want to get errata notifications? Sign up here.