Skip to content
VulniPulse
Advisory severityHigh7.0Red Hat Linux

High [CVE-2026-64219] Validate payload length and link_index in dc_process_dmub_aux_transfer_async

This high-severity Red Hat Linux advisory covers CVE-2026-64219 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-64219 Source published Source updated

VulniPulse record published Record updated

CVE-2026-64219
Affected products & platforms
Red Hat LinuxLinux Kernel
Open source advisory

Get an email when Red Hat Linux Linux Kernel publishes the next one.

See Red Hat Linux Linux Kernel's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat Linux Linux Kernel

Summary

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) This vulnerability is rated as Important rather than Moderate because successful exploitation allows a local user to corrupt kernel memory, potentially achieving elevated privileges or destabilizing the operating system.

Exposure is limited to environments where AMD display hardware is present and the corresponding kernel driver is active, which is uncommon on standard headless enterprise servers. Systems operating without AMD GPU hardware or running virtualized environments without physical GPU pass-through do not execute the vulnerable display engine paths.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.

Official advisory · high-confidence parse· fetched 3 days ago·verify at source

Fixed versions
  • kernel-0:6.12.0-211.49.1.el10_2
  • kernel-rt-0:4.18.0-553.156.1.rt7.497.el8_10
  • kernel-0:4.18.0-553.156.1.el8_10
  • kernel-0:5.14.0-687.41.1.el9_8
  • RHSA-2026:57251
  • RHSA-2026:55765
  • RHSA-2026:55764
  • RHSA-2026:57252

Official advisory · high-confidence parse· fetched 3 days ago·verify at source

Mitigation

Upgrade to a fixed release: kernel-0:6.12.0-211.49.1.el10_2, kernel-rt-0:4.18.0-553.156.1.rt7.497.el8_10, kernel-0:4.18.0-553.156.1.el8_10, kernel-0:5.14.0-687.41.1.el9_8, RHSA-2026:57251, RHSA-2026:55765. That is the remediation for this advisory.

The vendor advisory may list interim mitigations or workarounds not captured here. Review it before change work.

Official advisory · high-confidence parse· fetched 3 days ago·verify at source

All Red Hat Linux advisories

iPhone and Android apps · New on the App Store

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.