CVE-2026-64330

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

HIGH
7.8
CVSS Score
Published: July 25, 2026 at 08:49 AM UTC
Updated: September 4, 2026 at 03:36 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%

Description

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().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.19 ≤ v < 5.10.2614.19 ≤ v < 5.15.2124.19 ≤ v < 6.1.1784.19 ≤ v < 6.12.964.19 ≤ v < 6.18.394.19 ≤ v < 6.6.1454.19 ≤ v < 7.1.44.19 ≤ v < 7.25.11 ≤ v < 5.15.2125.16 ≤ v < 6.1.1786.13 ≤ v < 6.18.396.19 ≤ v < 7.1.46.2 ≤ v < 6.6.1456.7 ≤ v < 6.12.964ab8c18d4d67321cc7b660559de17511d4fc02377.2 rc17.2 rc2
Vendor states this is fixed in 012406f89abc52d1d5f07aa5653b519ebf6d2407 (fixed)
Vendor states this is fixed in 313ca06e7e224ca1dfadd5722fe71fb8bc276b8b (fixed)
Vendor states this is fixed in 3e1b1ac47e8163627f159f30d80d51b914620dd4 (fixed)
Vendor states this is fixed in 7b681dd5fbf60b24a13c14661e5b7735759fb491 (fixed)
Vendor states this is fixed in 89ff289cbf5d3b659a2babc5ccaae4eaf7e7cf53 (fixed)
Vendor states this is fixed in c6d2af3b217a525741c472f0ab45d7d274b8468f (fixed)
Vendor states this is fixed in d638ec188e95fe60f4b01106ffd41958f8fb3c2c (fixed)
Vendor states this is fixed in f8163c414de8640f2ca82ce4dc93409d4cdc2fad (fixed)
Vendor states this is fixed in 4.19 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.96 (unaffected)
Vendor states this is fixed in 6.18.39 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.4 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-129

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card