CVE-2026-64330

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-25. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

usb: typec: tcpm: Validate SVID index in svdm_consume_modes()

In svdm_consume_modes(), the SVID value is read from pmdata->svids using pmdata->svid_index as an array index without bounds validation:

paltmode->svid = pmdata->svids[pmdata->svid_index];

If pmdata->svid_index is driven beyond SVID_DISCOVERY_MAX (16), it results in an out-of-bounds read of the pmdata->svids array. Because pd_mode_data is embedded inside struct tcpm_port, indexing past svids reads into adjacent fields. In particular:

  • At index 16, it reads the altmodes count.
  • At index 18 and beyond, it reads into altmode_desc[], which contains
partner-supplied SVDM Discovery Modes VDOs.

By injecting a chosen SVID into altmode_desc[0].vdo and driving svid_index to 20, the partner can force paltmode->svid to be loaded with an arbitrary, partner- chosen SVID, which is then registered via typec_partner_register_altmode().

Fix this by validating that pmdata->svid_index is non-negative and strictly less than pmdata->nsvids before accessing the pmdata->svids array inside svdm_consume_modes().

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 25, 2026

Last Modified

September 4, 2026

Advisory Details (8)

Auto-updated Sep 4, 2026
No patch confirmed yet.
generic

usb: typec: tcpm: Validate SVID index in svdm_consume_modes() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f8163c414de8640f2ca82ce4dc93409d4cdc2fad
generic

usb: typec: tcpm: Validate SVID index in svdm_consume_modes() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d638ec188e95fe60f4b01106ffd41958f8fb3c2c
generic

usb: typec: tcpm: Validate SVID index in svdm_consume_modes() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c6d2af3b217a525741c472f0ab45d7d274b8468f
generic

usb: typec: tcpm: Validate SVID index in svdm_consume_modes() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/89ff289cbf5d3b659a2babc5ccaae4eaf7e7cf53
generic

usb: typec: tcpm: Validate SVID index in svdm_consume_modes() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7b681dd5fbf60b24a13c14661e5b7735759fb491
generic

usb: typec: tcpm: Validate SVID index in svdm_consume_modes() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3e1b1ac47e8163627f159f30d80d51b914620dd4
generic

usb: typec: tcpm: Validate SVID index in svdm_consume_modes() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/313ca06e7e224ca1dfadd5722fe71fb8bc276b8b
generic

usb: typec: tcpm: Validate SVID index in svdm_consume_modes() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/012406f89abc52d1d5f07aa5653b519ebf6d2407

Vendor Advisories for CVE-2026-64330(2)

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

Patch Availability(5)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

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 (158 versions)7.1.4-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 25× in last 7d / 73× 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.

Showing the most recent 100 of 118 total refreshes for this CVE.

  1. 2026-09-18 19:51 UTCEG score recompute
  2. 2026-09-18 19:51 UTCVendor advisory
  3. 2026-09-18 19:51 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 02:49 UTCEG score recompute
  6. 2026-09-18 02:49 UTCVendor advisory
  7. 2026-09-18 02:49 UTCGHSA enrichment
  8. 2026-09-17 01:56 UTCEG score recompute
  9. 2026-09-17 01:56 UTCVendor advisory
  10. 2026-09-17 01:56 UTCGHSA enrichment
  11. 2026-09-16 14:08 UTCEPSS rescore
  12. 2026-09-16 06:33 UTCEG score recompute
  13. 2026-09-16 06:33 UTCVendor advisory
  14. 2026-09-16 06:33 UTCGHSA enrichment
  15. 2026-09-16 05:15 UTCEPSS rescore
  16. 2026-09-15 09:26 UTCEG score recompute
  17. 2026-09-15 09:26 UTCVendor advisory
  18. 2026-09-15 09:26 UTCGHSA enrichment
  19. 2026-09-14 10:43 UTCVendor advisory
  20. 2026-09-14 10:43 UTCGHSA enrichment
  21. 2026-09-13 21:33 UTCEG score recompute
  22. 2026-09-13 21:33 UTCVendor advisory
  23. 2026-09-13 21:33 UTCGHSA enrichment
  24. 2026-09-13 08:00 UTCVendor advisory
  25. 2026-09-13 07:59 UTCGHSA enrichment
Show 75 more
  1. 2026-09-12 18:50 UTCEG score recompute
  2. 2026-09-12 18:50 UTCVendor advisory
  3. 2026-09-12 18:50 UTCGHSA enrichment
  4. 2026-09-12 05:37 UTCVendor advisory
  5. 2026-09-12 05:37 UTCGHSA enrichment
  6. 2026-09-11 16:27 UTCEG score recompute
  7. 2026-09-11 16:27 UTCVendor advisory
  8. 2026-09-11 16:27 UTCGHSA enrichment
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-11 09:37 UTCEPSS rescore
  11. 2026-09-11 02:40 UTCVendor advisory
  12. 2026-09-11 02:40 UTCGHSA enrichment
  13. 2026-09-10 13:28 UTCEG score recompute
  14. 2026-09-10 13:28 UTCVendor advisory
  15. 2026-09-10 13:28 UTCGHSA enrichment
  16. 2026-09-09 08:38 UTCEG score recompute
  17. 2026-09-09 08:38 UTCVendor advisory
  18. 2026-09-09 08:38 UTCGHSA enrichment
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-07 21:18 UTCEG score recompute
  21. 2026-09-07 21:18 UTCVendor advisory
  22. 2026-09-07 21:18 UTCGHSA enrichment
  23. 2026-09-07 16:01 UTCEPSS rescore
  24. 2026-09-06 13:47 UTCEPSS rescore
  25. 2026-09-06 09:26 UTCGHSA enrichment
  26. 2026-09-05 20:00 UTCEG score recompute
  27. 2026-09-05 20:00 UTCGHSA enrichment
  28. 2026-09-05 15:31 UTCEPSS rescore
  29. 2026-09-05 06:50 UTCEG score recompute
  30. 2026-09-05 06:50 UTCGHSA enrichment
  31. 2026-09-04 15:00 UTCEG score recompute 7.80
  32. 2026-09-04 15:00 UTCGHSA enrichment
  33. 2026-09-04 14:59 UTCNVD updateCVSS v3 → 7.8 · severity → HIGH
  34. 2026-09-04 12:42 UTCGHSA enrichment
  35. 2026-09-04 05:07 UTCEPSS rescore
  36. 2026-09-02 14:12 UTCEPSS rescore
  37. 2026-09-01 13:54 UTCEPSS rescore
  38. 2026-09-01 04:40 UTCEPSS rescore
  39. 2026-08-30 19:17 UTCEPSS rescore
  40. 2026-08-30 01:22 UTCEPSS rescore
  41. 2026-08-30 00:10 UTCGHSA enrichment
  42. 2026-08-28 21:42 UTCEPSS rescore
  43. 2026-08-26 14:47 UTCEPSS rescore
  44. 2026-08-26 13:44 UTCGHSA enrichment
  45. 2026-08-25 13:49 UTCEPSS rescore
  46. 2026-08-23 10:56 UTCGHSA enrichment
  47. 2026-08-23 00:19 UTCEPSS rescore
  48. 2026-08-21 23:49 UTCEPSS rescore
  49. 2026-08-20 08:08 UTCGHSA enrichment
  50. 2026-08-19 17:04 UTCEPSS rescore
  51. 2026-08-18 13:48 UTCEPSS rescore
  52. 2026-08-17 13:47 UTCEPSS rescore
  53. 2026-08-17 05:25 UTCNVD update
  54. 2026-08-17 05:20 UTCGHSA enrichment
  55. 2026-08-17 05:05 UTCMITRE cvelistV5
  56. 2026-08-16 14:56 UTCEPSS rescore
  57. 2026-08-15 01:30 UTCEPSS rescore
  58. 2026-08-14 17:56 UTCGHSA enrichment
  59. 2026-08-13 22:00 UTCEPSS rescore
  60. 2026-08-12 13:51 UTCEPSS rescore
  61. 2026-08-11 15:08 UTCGHSA enrichment
  62. 2026-08-11 00:00 UTCEPSS rescore
  63. 2026-08-10 18:19 UTCGHSA enrichment
  64. 2026-08-09 13:47 UTCEPSS rescore
  65. 2026-08-08 16:37 UTCEPSS rescore
  66. 2026-08-07 15:26 UTCGHSA enrichment
  67. 2026-08-06 13:47 UTCEPSS rescore
  68. 2026-08-05 19:17 UTCEPSS rescore
  69. 2026-08-05 19:17 UTCEPSS rescore
  70. 2026-08-04 15:10 UTCEPSS rescore
  71. 2026-08-04 12:39 UTCGHSA enrichment
  72. 2026-08-04 10:39 UTCEPSS rescore
  73. 2026-08-03 10:36 UTCEPSS rescore
  74. 2026-08-02 02:27 UTCEPSS rescore
  75. 2026-08-01 08:27 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-64330?
CVE-2026-64330 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpm: Validate SVID index in svdmconsumemodes() In svdmconsumemodes(), the SVID value is read from pmdata->svids using pmdata->svid_index as an array index without bounds validation: paltmode->svid =…
When was CVE-2026-64330 disclosed?
CVE-2026-64330 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on September 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64330 actively exploited?
CVE-2026-64330 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 97.0% of all scored CVEs.
What is the CVSS score of CVE-2026-64330?
CVE-2026-64330 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64330?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64330, 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-64330

Explore →

Is Your Infrastructure Affected by CVE-2026-64330?

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