Linux Kernel up to 7.2-rc2 typec/tcpm svdm_consume_modes svid_index out-of-bounds

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.0$0-$5k3.18-

Summaryinfo

A vulnerability marked as critical has been reported in Linux Kernel up to 7.2-rc2. This affects the function svdm_consume_modes of the component typec/tcpm. Performing a manipulation of the argument svid_index results in out-of-bounds. This vulnerability is identified as CVE-2026-64330. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability classified as critical has been found in Linux Kernel up to 7.2-rc2. This affects the function svdm_consume_modes of the component typec/tcpm. The manipulation of the argument svid_index with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-64330 since 07/19/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/25/2026).

Upgrading to version 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96, 6.18.39, 7.1.4 or 7.2-rc3 eliminates this vulnerability. Applying the patch 89ff289cbf5d3b659a2babc5ccaae4eaf7e7cf53/d638ec188e95fe60f4b01106ffd41958f8fb3c2c/f8163c414de8640f2ca82ce4dc93409d4cdc2fad/012406f89abc52d1d5f07aa5653b519ebf6d2407/c6d2af3b217a525741c472f0ab45d7d274b8468f/3e1b1ac47e8163627f159f30d80d51b914620dd4/313ca06e7e224ca1dfadd5722fe71fb8bc276b8b/7b681dd5fbf60b24a13c14661e5b7735759fb491 is able to eliminate this problem.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 7.0

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Out-of-bounds
CWE: CWE-125 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.261/5.15.212/6.1.178/6.6.145/6.12.96/6.18.39/7.1.4/7.2-rc3
Patch: 89ff289cbf5d3b659a2babc5ccaae4eaf7e7cf53/d638ec188e95fe60f4b01106ffd41958f8fb3c2c/f8163c414de8640f2ca82ce4dc93409d4cdc2fad/012406f89abc52d1d5f07aa5653b519ebf6d2407/c6d2af3b217a525741c472f0ab45d7d274b8468f/3e1b1ac47e8163627f159f30d80d51b914620dd4/313ca06e7e224ca1dfadd5722fe71fb8bc276b8b/7b681dd5fbf60b24a13c14661e5b7735759fb491

Timelineinfo

07/19/2026 CVE reserved
07/25/2026 +6 days Advisory disclosed
07/25/2026 +0 days VulDB entry created
07/25/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-64330 (🔒)
GCVE (CVE): GCVE-0-2026-64330
GCVE (VulDB): GCVE-100-383121

Entryinfo

Created: 07/25/2026 15:32
Changes: 07/25/2026 15:32 (60)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!