CVE-2026-64351

UNRATEDCVSS · not yet scoredTrending — 3 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:

net: usb: kalmia: bound RX frame length in kalmia_rx_fixup()

kalmia_rx_fixup() computes usb_packet_length = skb->len - (2 * KALMIA_HEADER_LENGTH) as a u16, guarded only by a pre-loop check that skb->len is at least KALMIA_HEADER_LENGTH, which is 6. A device can deliver a short bulk-IN frame with skb->len in the 6 to 11 range, or leave a short trailing remainder on a later loop iteration. Either case underflows usb_packet_length to about 65530.

That bypasses the usb_packet_length < ether_packet_length truncation path. The device-supplied ether_packet_length, a le16 up to 65535 read from header_start[2], then drives a memcmp() and the following skb_trim() and skb_pull() past the end of the rx buffer. The rx buffer is hard_mtu * 10, which is 14000 bytes. That is an out of bounds read.

Require both the start and end framing headers to be present before subtracting them, on every loop iteration.

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

July 25, 2026

Last Modified

August 17, 2026

Vendor Advisories for CVE-2026-64351(2)

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

Affected Packages

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1
linux-6.126.12.100-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.4-1

Data Freshness Timeline

(refreshed 8× in last 7d / 44× 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-30 01:22 UTCEPSS rescore
  2. 2026-08-28 21:42 UTCEPSS rescore
  3. 2026-08-27 01:23 UTCVendor advisory
  4. 2026-08-27 01:23 UTCGHSA enrichment
  5. 2026-08-26 14:47 UTCEPSS rescore
  6. 2026-08-25 13:49 UTCEPSS rescore
  7. 2026-08-23 18:46 UTCVendor advisory
  8. 2026-08-23 18:46 UTCGHSA enrichment
  9. 2026-08-21 23:49 UTCEPSS rescore
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-20 12:11 UTCVendor advisory
  12. 2026-08-20 12:11 UTCGHSA enrichment
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 05:25 UTCNVD update
  17. 2026-08-17 05:19 UTCVendor advisory
  18. 2026-08-17 05:19 UTCGHSA enrichment
  19. 2026-08-17 05:05 UTCMITRE cvelistV5
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-14 21:44 UTCVendor advisory
  23. 2026-08-14 21:44 UTCGHSA enrichment
  24. 2026-08-13 22:00 UTCEPSS rescore
  25. 2026-08-12 13:51 UTCEPSS rescore
Show 35 more
  1. 2026-08-11 15:08 UTCVendor advisory
  2. 2026-08-11 15:08 UTCGHSA enrichment
  3. 2026-08-11 11:48 UTCVendor advisory
  4. 2026-08-11 11:48 UTCGHSA enrichment
  5. 2026-08-11 00:00 UTCEPSS rescore
  6. 2026-08-09 13:47 UTCEPSS rescore
  7. 2026-08-08 16:37 UTCEPSS rescore
  8. 2026-08-08 05:12 UTCGHSA enrichment
  9. 2026-08-06 13:47 UTCEPSS rescore
  10. 2026-08-05 19:17 UTCEPSS rescore
  11. 2026-08-05 19:17 UTCEPSS rescore
  12. 2026-08-04 22:37 UTCGHSA enrichment
  13. 2026-08-04 15:10 UTCEPSS rescore
  14. 2026-08-04 10:39 UTCEPSS rescore
  15. 2026-08-03 10:36 UTCEPSS rescore
  16. 2026-08-02 02:27 UTCEPSS rescore
  17. 2026-08-01 16:01 UTCEG score recompute
  18. 2026-08-01 16:01 UTCGHSA enrichment
  19. 2026-08-01 04:16 UTCEPSS rescore
  20. 2026-07-30 16:28 UTCEPSS rescore
  21. 2026-07-30 01:30 UTCEPSS rescore
  22. 2026-07-30 01:30 UTCEPSS rescore
  23. 2026-07-29 09:25 UTCEG score recompute
  24. 2026-07-29 09:25 UTCGHSA enrichment
  25. 2026-07-28 15:37 UTCEPSS rescore
  26. 2026-07-27 14:14 UTCEPSS rescore
  27. 2026-07-26 14:54 UTCEPSS rescore
  28. 2026-07-26 14:54 UTCEPSS rescore
  29. 2026-07-26 02:49 UTCEG score recompute
  30. 2026-07-26 02:49 UTCGHSA enrichment
  31. 2026-07-25 14:18 UTCEPSS rescore
  32. 2026-07-25 14:18 UTCEPSS rescore
  33. 2026-07-25 10:39 UTCNVD update
  34. 2026-07-25 09:37 UTCEG score recompute
  35. 2026-07-25 09:21 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-64351?
CVE-2026-64351 is a publicly disclosed vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net: usb: kalmia: bound RX frame length in kalmiarxfixup() kalmiarxfixup() computes usbpacketlength = skb->len - (2 * KALMIAHEADERLENGTH) as a u16, guarded only by a pre-loop check that skb->len is at least KALMIAHEADERLENGTH,…
When was CVE-2026-64351 disclosed?
CVE-2026-64351 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64351 actively exploited?
CVE-2026-64351 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 91.8% of all scored CVEs.
How do I remediate CVE-2026-64351?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64351, 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-64351

Explore →

Is Your Infrastructure Affected by CVE-2026-64351?

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