Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2026-64219

7.0 · HIGH

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_tra…

Published Jul 24, 2026CWE-674EPSS 0.14%

Overview

CVE-2026-64219 is a high-severity vulnerability. It was published on July 24, 2026 and has a CVSS 3.1 base score of 7.0 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.0, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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)

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/16a5fa57565afb6bf37e18129921c270c93d8e2bRefgit.kernel.org/stable/c/1c8c6e912f2945b2a3e669afca6b52174b88e86eRefgit.kernel.org/stable/c/1ecde19bfce6535bffddad1139ff466b6d401b8eRefgit.kernel.org/stable/c/3265f3ed373fb8048be713aadcdf702579a0e53dRefgit.kernel.org/stable/c/6c92f6d9600efa3ef0d9e560a2b52776d9803c29Refgit.kernel.org/stable/c/90c398e822ca76e40548df0c061dd4f93ea92d71Refgit.kernel.org/stable/c/d6590e3f766e3111dd1beaf88b9384d117acfa6b

How CyberStrike helps

Frequently asked questions

What is CVE-2026-64219?

CVE-2026-64219 is a high-severity vulnerability. It was published on July 24, 2026 and has a CVSS 3.1 base score of 7.0 (HIGH).

How severe is CVE-2026-64219?

This vulnerability has a CVSS 3.1 base score of 7.0, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-64219?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-64219?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-64219 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999