usb: typec: tipd: fix uninitialized typec_partner_desc in cd321x_update_work()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.567.2.107.3In the Linux kernel, the following vulnerability has been resolved:
usb: typec: tipd: fix uninitialized typec_partner_desc in cd321x_update_work()
cd321x_update_work() 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.
From the CVE record · Linux
The Linux kernel’s USB Type-C tipd driver passes a partially initialized partner descriptor to typec_register_partner(). When a USB device is linked to the port, an unset callback may be invoked; other unset fields can expose stack data through partner sysfs. The input does not specify attacker access or authentication requirements.
Engineers running Linux kernels with the affected USB Type-C tipd driver should check their kernel version; affected versions are not specified.