CVE-2026-99623

Description

A flaw was found in the Linux kernel's AMDGPU graphics driver. When querying display backlight capabilities, the driver does not validate that the number of curve points reported by system firmware fits within its fixed-size buffer. A malformed firmware table supplying an excessive number of points causes the driver to access memory outside the designated buffer bounds, which can lead to kernel memory corruption or a system crash resulting in a Denial of Service (DoS).

Statement

This vulnerability is rated as Moderate severity for Red Hat products because triggering the issue requires local access on systems equipped with AMD graphics hardware and malformed ACPI firmware tables, with the impact confined to a denial of service. In typical enterprise server deployments, graphical display devices and the associated AMDGPU driver stack are either absent or unused, significantly reducing exposure. Systems lacking AMD display adapters or running compliant firmware that adheres to backlight specification limits are not affected.

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.4N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/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:L/PR:H/UI:N/S:U/C:N/I:N/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.