CVE-2026-64219
What it is
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)
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.0 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-674
- Record status
- Modified
Affected
- Linux Kernel < 5.15.209
- Linux Kernel < 6.1.175
- Linux Kernel < 6.6.142
- Linux Kernel < 6.12.92
- Linux Kernel < 6.18.34
- Linux Kernel < 7.0.11
- Linux Kernel 7.1
Attack profile CVSS 3.1 · 7.0
- Attack vector
- Local
- Complexity
- High
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-64219.md and follow it. Check whether this project is affected by CVE-2026-64219. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/16a5fa57565afb6bf37e18129921c270c93d8e2b
- https://git.kernel.org/stable/c/1c8c6e912f2945b2a3e669afca6b52174b88e86e
- https://git.kernel.org/stable/c/1ecde19bfce6535bffddad1139ff466b6d401b8e
- https://git.kernel.org/stable/c/3265f3ed373fb8048be713aadcdf702579a0e53d
- https://git.kernel.org/stable/c/6c92f6d9600efa3ef0d9e560a2b52776d9803c29
- https://git.kernel.org/stable/c/90c398e822ca76e40548df0c061dd4f93ea92d71
- https://git.kernel.org/stable/c/d6590e3f766e3111dd1beaf88b9384d117acfa6b
References
- https://git.kernel.org/stable/c/16a5fa57565afb6bf37e18129921c270c93d8e2b
- https://git.kernel.org/stable/c/1c8c6e912f2945b2a3e669afca6b52174b88e86e
- https://git.kernel.org/stable/c/1ecde19bfce6535bffddad1139ff466b6d401b8e
- https://git.kernel.org/stable/c/3265f3ed373fb8048be713aadcdf702579a0e53d
- https://git.kernel.org/stable/c/6c92f6d9600efa3ef0d9e560a2b52776d9803c29
- https://git.kernel.org/stable/c/90c398e822ca76e40548df0c061dd4f93ea92d71
- https://git.kernel.org/stable/c/d6590e3f766e3111dd1beaf88b9384d117acfa6b