PT-2026-64551 · Linux · Linux
CVE-2026-64330
·
Published
2026-07-25
·
Updated
2026-07-25
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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().
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Linux