CVE-2026-64330

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

Gravité et risque d'exploitation

CVE-2026-64330 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.13 %, ce qui la place devant 2.3 % des CVE référencées.

Que faire ?

• Vérifiez si Linux (versions <=6.1.*, <=6.12.*, 6.18.39, 0, <=7.1.*, 7.1.4, <3e1b1ac47e8163627f159f30d80d51b914620dd4, <7b681dd5fbf60b24a13c14661e5b7735759fb491, 4.19, 6.1.178, <=5.10.*, <=6.6.*, <012406f89abc52d1d5f07aa5653b519ebf6d2407, <313ca06e7e224ca1dfadd5722fe71fb8bc276b8b, <f8163c414de8640f2ca82ce4dc93409d4cdc2fad, <c6d2af3b217a525741c472f0ab45d7d274b8468f, <=6.18.*, <d638ec188e95fe60f4b01106ffd41958f8fb3c2c, 5.15.212, 6.6.145, 5.10.261, <4.19, <=*, <=5.15.*, <89ff289cbf5d3b659a2babc5ccaae4eaf7e7cf53, 4ab8c18d4d67321cc7b660559de17511d4fc0237, 6.12.96, 7.2) est présent sur votre parc.
• Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
• À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
• Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références

• https://git.kernel.org/stable/c/89ff289cbf5d3b659a2babc5ccaae4eaf7e7cf53
• https://git.kernel.org/stable/c/d638ec188e95fe60f4b01106ffd41958f8fb3c2c
• https://git.kernel.org/stable/c/f8163c414de8640f2ca82ce4dc93409d4cdc2fad
• https://git.kernel.org/stable/c/012406f89abc52d1d5f07aa5653b519ebf6d2407
• https://git.kernel.org/stable/c/c6d2af3b217a525741c472f0ab45d7d274b8468f
• https://git.kernel.org/stable/c/3e1b1ac47e8163627f159f30d80d51b914620dd4
• https://git.kernel.org/stable/c/313ca06e7e224ca1dfadd5722fe71fb8bc276b8b
• https://git.kernel.org/stable/c/7b681dd5fbf60b24a13c14661e5b7735759fb491