CVE-2026-64565: Input: ims-pcu - fix heap-buffer-overflow in ims_pcu_process_data()
In the Linux kernel, the following vulnerability has been resolved:
Input: ims-pcu - fix heap-buffer-overflow in imspcuprocessdata()
The imspcuprocessdata() processes incoming URB data byte by byte. However, it fails to check if the readpos index exceeds IMSPCUBUFSIZE.
If a malicious USB device sends a packet larger than IMSPCUBUFSIZE, readpos will increment indefinitely. Moreover, since readpos is located immediately after readbuf, the attacker can overwrite readpos itself to arbitrarily control the index.
This manipulated readpos is subsequently used in imspcuhandleresponse() to copy data into cmdbuf, leading to a heap buffer overflow.
Specifically, an attacker can overwrite the cmddone.wait.head located at offset 136 relative to cmdbuf in the imspcuhandleresponse(). Consequently, when the driver calls complete(&pcu->cmddone), it triggers a control flow hijack by using the manipulated pointer.
Fix this by adding a bounds check for readpos before writing to readbuf. If the packet is too long, discard it, log a warning, and reset the parser state.
[dtor: factor out resetting packet state, reset checksum as well]
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.150.1-1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-64565?
CVE-2026-64565 has a risk rating of 80, indicating a high severity vulnerability.
How do I fix CVE-2026-64565?
To fix CVE-2026-64565, update to the latest patched version of the Linux kernel that addresses the heap-buffer overflow.
What systems are affected by CVE-2026-64565?
CVE-2026-64565 affects versions of the Linux kernel that include the ims-pcu component.
What type of vulnerability is CVE-2026-64565?
CVE-2026-64565 is classified as a buffer overflow vulnerability.
What could happen if CVE-2026-64565 is exploited?
Exploitation of CVE-2026-64565 could allow a malicious user to cause a heap-buffer overflow, potentially leading to arbitrary code execution.