Description
In the Linux kernel, the following vulnerability has been resolved:

drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async

[Why&How]
dc_process_dmub_aux_transfer_async() copies payload->length bytes into a
16-byte stack buffer (dpaux.data[16]) guarded only by an ASSERT(), which
is a no-op in release builds. If a caller ever passes length > 16 this
results in a stack buffer overflow via memcpy.

Additionally, link_index is used to dereference dc->links[] without
bounds checking against dc->link_count, risking an out-of-bounds access.

Replace the ASSERT with a hard runtime check that returns false when
payload->length exceeds the destination buffer size, and add a bounds
check for link_index before it is used.

(cherry picked from commit ba4caa9fecdf7a38f98c878ad05a8a64148b6881)
Published: 2026-07-24
Score: 7 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A stack AMD display driver when dc_process_dmub_aux_transfer_async copies a payload whose length exceeds 16 bytes into a 16‑byte stack buffer guarded only by an ASSERT that is a no‑op in release builds. Additionally, link_index is used to index the dc->links[] array without bounds checking, risking an out‑of‑bounds access. If triggered successfully, these defects can corrupt kernel memory and enable an attacker to execute arbitrary code in the context of the kernel.

Affected Systems

The flaw resides in the Linux kernel’s AMD display driver (drm/amd/display). All Linux kernel versions built before the inclusion of commit ba4caa9fecdf7a38f98c878ad05a8a64148b6881 are affected. No specific vendor product names beyond the Linux kernel are mentioned, so any system running an unpatched kernel that includes this driver is at risk.

Risk and Exploitability

The EPSS score is reported as less than 1 percent, indicating a low probability of exploitation at present. The vulnerability is not listed in the CISA KEV catalog. While the flaw is a kernel‑space buffer overflow, its exploitation requires gaining the ability to invoke the vulnerable function, which typically means possessing load a malicious module. The likely attack vector is local; remote exploitation would depend on additional indirect vulnerabilities that could lead to kernel execution. Once the kernel is patched to include the runtime check and bound checking, the vulnerability is mitigated.

Generated by OpenCVE AI on August 13, 2026 at 11:42 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the kernel to a version that contains commit ba4caa9fecdf7a38f98c878ad05a8a64148b6881, which replaces the ASSERT.
  • Ensure that the kernel’s module verification is enabled or unsigned module loading is disabled to reduce the risk of malicious modules leveraging this vulnerability.
  • If AMD display functionality is not required, compile the kernel without the DRM_AMD_DISPLAY driver to eliminate the vulnerability.

Generated by OpenCVE AI on August 13, 2026 at 11:42 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Ubuntu USN Ubuntu USN USN-8618-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8620-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8620-2 Linux kernel (Azure FIPS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8620-3 Linux kernel (Intel IoTG) vulnerabilities
Ubuntu USN Ubuntu USN USN-8620-4 Linux kernel (Intel IoTG) vulnerabilities
History

Tue, 11 Aug 2026 18:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-674
CPEs cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:*

Tue, 28 Jul 2026 16:15:00 +0000


Mon, 27 Jul 2026 05:15:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}


Fri, 24 Jul 2026 18:30:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async [Why&How] dc_process_dmub_aux_transfer_async() copies payload->length bytes into a 16-byte stack buffer (dpaux.data[16]) guarded only by an ASSERT(), which is a no-op in release builds. If a caller ever passes length > 16 this results in a stack buffer overflow via memcpy. Additionally, link_index is used to dereference dc->links[] without bounds checking against dc->link_count, risking an out-of-bounds access. Replace the ASSERT with a hard runtime check that returns false when payload->length exceeds the destination buffer size, and add a bounds check for link_index before it is used. (cherry picked from commit ba4caa9fecdf7a38f98c878ad05a8a64148b6881)
Title drm/amd/display: Validate payload length and link_index in dc_process_dmub_aux_transfer_async
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-05T12:40:07.374Z

Reserved: 2026-07-19T15:36:31.770Z

Link: CVE-2026-64219

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Analyzed

Published: 2026-07-24T16:16:49.670

Modified: 2026-08-11T18:25:59.640

Link: CVE-2026-64219

cve-icon Redhat

Severity :

Publid Date: 2026-07-24T00:00:00Z

Links: CVE-2026-64219 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-13T11:45:03Z

Weaknesses
  • CWE-120

    Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

  • CWE-674

    Uncontrolled Recursion