Live › vulnerability › CVE-2026-98760
Go to dashboardThe Linux kernel's TPS6598x USB Type-C port driver registers a partner descriptor from uninitialized stack memory, so callback pointers and fields can hold garbage. The bad function pointers can be invoked when a USB device is linked to the port, and sysfs exposes leaked stack data.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with the TI TPS6598x USB Type-C port controller driver (usb: typec: tipd), typically laptops or boards using that controller. Systems without this hardware or driver are not affected. The sources do not say which kernel versions are vulnerable.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
usb: typec: tipd: fix uninitialized typec_partner_desc in tps6598x_connect()
tps6598x_connect() passes a stack-allocated typec_partner_desc to typec_register_partner() after initializing only usb_pd, accessory and identity.
typec_register_partner() copies attach and deattach from the descriptor into the partner. With those fields left unset, garbage function pointers may be stored and later invoked from typec_partner_link_device() when a USB device is linked to the port. Uninitialized pd_revision and usb_capability similarly leak stack data through partner sysfs.
Zero-initialize the descriptor so optional callbacks remain NULL and the remaining fields are zero.
This page as .md · .json · in your agent: get_signal("CVE-2026-98760")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.