AMDGPU VCN4 Out-of-Bounds Read in Linux Kernel

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/vcn4: Prevent OOB reads when parsing dec msg Check bounds against the end of the BO whenever we access the msg.

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-46199

EUVD

EUVD-2026-32826

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 5.13 (inc) to 6.1.175 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-125	The product reads data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

Executive Summary

This vulnerability exists in the Linux kernel, specifically in the drm/amdgpu/vcn4 component. It involves out-of-bounds (OOB) reads when parsing decode messages (dec msg). The issue arises because the code did not properly check bounds against the end of the buffer object (BO) when accessing the message, which could lead to reading memory beyond the intended limits.

Impact Analysis

An out-of-bounds read vulnerability can potentially lead to information disclosure or cause system instability. By reading memory beyond the intended buffer, an attacker might access sensitive data or cause unexpected behavior in the system, which could be exploited depending on the context and privileges.

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

0/70