CVE-2026-99466

Description

A flaw was found in the Linux kernel's Microchip CSI-2 Demux Controller (CSI2DC) driver. This vulnerability can allow a local attacker to cause a Denial of Service (DoS) through a use-after-free condition. When device initialization fails after registering an asynchronous notification handler, the error-handling path frees the underlying device memory without unregistering the handler from the global notifier list. Subsequent kernel access to this list results in memory corruption and a system crash.

Statement

This vulnerability is rated as Moderate impact for Red Hat enterprise products because exploitation requires specialized hardware platforms and elevated privileges to trigger driver initialization failures, limiting the blast radius to a localized denial of service. The affected Microchip CSI-2 Demux Controller is an embedded video capture interface typically found in specific system-on-chip architectures, which is not present in standard enterprise server hardware. Under standard configurations, systems without this hardware device are not exposed to the condition leading to memory corruption or kernel 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 Score4.1N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredHighN/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:H/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.