CVE-2026-64219 affects the Linux kernel AMD display driver's dc_process_dmub_aux_transfer_async() function. The function copies payload->length bytes into a 16-byte stack buffer using memcpy, relying on an ASSERT() that is ineffective in release builds. A payload length exceeding 16 bytes therefore causes a stack buffer overflow. The function also uses link_index to access dc->links[] without checking it against dc->link_count, creating a potential out-of-bounds access. These validation failures can cause kernel memory corruption and potentially denial of service or kernel-context code execution.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
36 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Insufficient validation of payload length and link_index in dc_process_dmub_aux_transfer_async within the Linux kernel AMD display driver.
A vulnerability covered by the Miracle Linux kernel package update. Individual technical details and exploit availability are not specified.
Linux kernel vulnerability fixed by USN-8802-1.
Linux kernel vulnerability addressed by Ubuntu USN-8761-1.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.