CVE-2026-64330
Last modified
CVE-2026-64330 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
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().
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.19, < 5.10.261 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.212 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.178 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.145 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.96 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.39 | — |
| Linux | Linux Kernel | >= 6.19, < 7.1.4 | — |
| Linux | Linux Kernel | 7.2 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64330?
How severe is CVE-2026-64330?
How do I fix CVE-2026-64330?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64325In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64326In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64327In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64328In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64329In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-6433The Custom css-js-php WordPress plugin through 2.0.7 does no…7.3
- CVE-2026-64331In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64332In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64333In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64334In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64335In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64336In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-64330?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
