CVE-2026-64097

Received Received - Intake

Out-of-Bounds Read in AMD Display Driver

Publication date: 2026-07-19

Last updated on: 2026-07-20

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Validate GPIO pin LUT table size before iterating [Why&How] The GPIO pin table parsers in get_gpio_i2c_info() and bios_parser_get_gpio_pin_info() derive an element count from the VBIOS table_header.structuresize field, then iterate over gpio_pin[] entries. However, GET_IMAGE() only validates that the table header itself fits within the BIOS image. If the VBIOS reports a structuresize larger than the actual mapped data, the loop reads past the end of the BIOS image, causing an out-of-bounds read. Fix this by calling bios_get_image() to validate that the full claimed structuresize is accessible within the BIOS image before entering the loop in both functions. (cherry picked from commit ba5e95b43b773ae1bf1f66ee6b31eb774e65afe3)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-19

Last Modified

2026-07-20

Generated

2026-07-20

AI Q&A

2026-07-19

EPSS Evaluated

N/A

NVD

CVE-2026-64097

EUVD

EUVD-2026-45782

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This is a Linux kernel vulnerability in the AMD display driver. It involves an out-of-bounds read in the GPIO pin table parsers. The issue occurs when the VBIOS reports a larger table size than the actual mapped data, causing the parser to read past the end of the BIOS image during iteration.

Detection Guidance

This vulnerability is specific to the Linux kernel's AMD display driver and involves an out-of-bounds read in the GPU driver. Detection requires checking the kernel version and AMD display driver code. Use uname -a to check the kernel version and grep for affected AMD display driver functions in the kernel source.

Impact Analysis

An attacker with local access could exploit this to read sensitive kernel memory, potentially leading to privilege escalation or system crashes. It may also allow unauthorized access to data processed by the GPU.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards. It is a low-level Linux kernel issue involving out-of-bounds reads in GPU driver code, which could potentially lead to memory corruption or crashes but does not inherently violate data protection or privacy regulations.

Mitigation Strategies

Update the Linux kernel to a patched version that includes the fix for this vulnerability. Monitor vendor advisories for AMD GPU driver updates and apply them promptly. If using a custom kernel, ensure the patch for drm/amd/display is applied.

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

0/70