CVE-2026-64219
Last modified
CVE-2026-64219 is a high-severity vulnerability rated 7/10 on the CVSS scale. 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). EPSS estimates a 0.14% chance of exploitation in the next 30 days.
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)
Metrics
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.13, < 5.15.209 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.175 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.142 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.92 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.34 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.11 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64219?
How severe is CVE-2026-64219?
How do I fix CVE-2026-64219?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64213In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64214In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64215In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64216In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64217In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64218In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64220In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64221In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64222In the Linux kernel, the following vulnerability has been re…7
- CVE-2026-64223In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-64224In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64225In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-64219?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
