CVE-2026-46218

Analyzed Analyzed - Analysis Complete

Bounds Checking Flaw in AMDGPU Linux Kernel Driver

Publication date: 2026-05-28

Last updated on: 2026-06-10

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Add bounds checking to ib_{get,set}_value The uvd/vce/vcn code accesses the IB at predefined offsets without checking that the IB is large enough. Check the bounds here. The caller is responsible for making sure it can handle arbitrary return values. Also make the idx a uint32_t to prevent overflows causing the condition to fail.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-05-28

Last Modified

2026-06-10

Generated

2026-07-08

AI Q&A

2026-05-28

EPSS Evaluated

2026-07-06

NVD

CVE-2026-46218

EUVD

EUVD-2026-32845

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	From 6.2 (inc) to 6.6.140 (exc)
linux	linux_kernel	From 6.13 (inc) to 6.18.32 (exc)
linux	linux_kernel	From 6.7 (inc) to 6.12.90 (exc)
linux	linux_kernel	From 6.19 (inc) to 7.0.9 (exc)
linux	linux_kernel	From 4.2 (inc) to 6.1.175 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability exists in the Linux kernel's drm/amdgpu component, specifically in the uvd/vce/vcn code. The issue is that the code accesses the IB (Indirect Buffer) at predefined offsets without verifying if the IB is large enough, which means it lacks proper bounds checking.

The vulnerability was addressed by adding bounds checking to the functions ib_get_value and ib_set_value to ensure that the IB is sufficiently large before accessing it. Additionally, the index variable was changed to a uint32_t type to prevent overflow conditions that could cause the bounds check to fail.

Impact Analysis

If exploited, this vulnerability could allow improper memory access due to lack of bounds checking when accessing the IB. This could potentially lead to unexpected behavior, crashes, or security issues such as information disclosure or privilege escalation depending on how the kernel handles the invalid accesses.

Hi! I’m here to help you understand CVE-2026-46218. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70