CVE-2026-64565Input: ims-pcu - fix heap-buffer-overflow in ims_pcu_process_data()
- —Not scoredno CVSS score yet
- 0.18%Exploitation in 30 daysEPSS · top 92% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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]
Timeline
ID reserved
By Linux
- 16 days later
· 16 days later
Published
- 15 days later
· 15 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Awaiting Analysis.
- EPSS (exploitation in 30 days)
- 0.18% · top 92% of all CVEs (14 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 628329d52474323938a03826941e166bc7c8eff4 – < 06cfff93fd40441292567b999091beab11c74504
- affected 628329d52474323938a03826941e166bc7c8eff4 – < 992a7173364dcf63e30012af43da3c2f279839f9
- affected 628329d52474323938a03826941e166bc7c8eff4 – < 3a801bc75ba1d121d0ed60e7234f93ba5651d87d
- affected 628329d52474323938a03826941e166bc7c8eff4 – < 40bbbf2e91fd60715525bf0405c67876af817edf
- affected 628329d52474323938a03826941e166bc7c8eff4 – < ca9f8c09845fb8c51b6d447f6428eecd1b8b0a49
- affected 628329d52474323938a03826941e166bc7c8eff4 – < d03a740e087de7dcb2a26dc1123377bd3d1d84ca
- affected 628329d52474323938a03826941e166bc7c8eff4 – < 875115b82c295277b81b6dfee7debc725f44e854
- affected 3.10
- unaffected < 3.10
- unaffected 5.10.265 – ≤ 5.10.*
- unaffected 5.15.216 – ≤ 5.15.*
- unaffected 6.1.183 – ≤ 6.1.*
- unaffected 6.6.148 – ≤ 6.6.*
- unaffected 6.12.101 – ≤ 6.12.*
- unaffected 6.18.42 – ≤ 6.18.*
- unaffected 7.1 – ≤ *
References
References7
- https://git.kernel.org/stable/c/06cfff93fd40441292567b999091beab11c74504 (opens in a new tab)
- https://git.kernel.org/stable/c/992a7173364dcf63e30012af43da3c2f279839f9 (opens in a new tab)
- https://git.kernel.org/stable/c/3a801bc75ba1d121d0ed60e7234f93ba5651d87d (opens in a new tab)
- https://git.kernel.org/stable/c/40bbbf2e91fd60715525bf0405c67876af817edf (opens in a new tab)
- https://git.kernel.org/stable/c/ca9f8c09845fb8c51b6d447f6428eecd1b8b0a49 (opens in a new tab)
- https://git.kernel.org/stable/c/d03a740e087de7dcb2a26dc1123377bd3d1d84ca (opens in a new tab)
- https://git.kernel.org/stable/c/875115b82c295277b81b6dfee7debc725f44e854 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-52606 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-64565)Record last updated .