CVE-2026-64565

UNRATEDCVSS · not yet scoredTrending — 5 sources updated this week
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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]

CVSS v3
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
EG Risk
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

August 4, 2026

Last Modified

August 19, 2026

Vendor Advisories for CVE-2026-64565(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (499 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (337 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.12.96-1 (32 versions)6.12.101-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (154 versions)7.1.3-1

Data Freshness Timeline

(refreshed 13× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-19 17:27 UTCVendor advisory
  3. 2026-08-19 17:27 UTCGHSA enrichment
  4. 2026-08-19 17:21 UTCNVD update
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-19 16:56 UTCVendor advisory
  7. 2026-08-19 16:56 UTCGHSA enrichment
  8. 2026-08-19 16:43 UTCMITRE cvelistV5
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-17 02:05 UTCVendor advisory
  11. 2026-08-17 02:05 UTCGHSA enrichment
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-13 21:24 UTCVendor advisory
  16. 2026-08-13 21:24 UTCGHSA enrichment
  17. 2026-08-12 13:51 UTCEPSS rescore
  18. 2026-08-11 00:00 UTCEPSS rescore
  19. 2026-08-10 16:41 UTCGHSA enrichment
  20. 2026-08-09 13:47 UTCEPSS rescore
  21. 2026-08-08 16:37 UTCEPSS rescore
  22. 2026-08-07 12:00 UTCEG score recompute
  23. 2026-08-07 12:00 UTCGHSA enrichment
  24. 2026-08-06 13:47 UTCEPSS rescore
  25. 2026-08-05 19:17 UTCEPSS rescore
Show 5 more
  1. 2026-08-05 19:17 UTCEPSS rescore
  2. 2026-08-04 15:10 UTCEPSS rescore
  3. 2026-08-04 07:17 UTCNVD update
  4. 2026-08-04 06:35 UTCEG score recompute
  5. 2026-08-04 06:33 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-64565?
CVE-2026-64565 is a publicly disclosed vulnerability published on August 4, 2026. In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - fix heap-buffer-overflow in imspcuprocess_data() The imspcuprocess_data() processes incoming URB data byte by byte. However, it fails to check if the read_pos index exceeds IMSPCUBUF_SIZE. If a malicious USB device…
When was CVE-2026-64565 disclosed?
CVE-2026-64565 was first published in the National Vulnerability Database on August 4, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64565 actively exploited?
CVE-2026-64565 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.4% of all scored CVEs.
How do I remediate CVE-2026-64565?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64565, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64565

Explore →

Is Your Infrastructure Affected by CVE-2026-64565?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.