usb: typec: displayport: Fix potential deadlock
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 10cc2cfd3e5d0e0ec7590c4bee8bcea10e5492c4 · < c782f98eef14197affa8a7b91e6981420f109ea9| No fix yet |
| Linux Linux |
| No fix yet |
In the Linux kernel, the following vulnerability has been resolved:
usb: typec: displayport: Fix potential deadlock
The deadlock can occur due to a recursive lock acquisition of `cros_typec_altmode_data::mutex`. The call chain is as follows: 1. cros_typec_altmode_work() acquires the mutex 2. typec_altmode_vdm() -> dp_altmode_vdm() -> 3. typec_altmode_exit() -> cros_typec_altmode_exit() 4. cros_typec_altmode_exit() attempts to acquire the mutex again
To prevent this, defer the `typec_altmode_exit()` call by scheduling it rather than calling it directly from within the mutex-protected context.
From the CVE record · Linux
The Linux kernel USB Type-C DisplayPort code can deadlock when an exit path tries to reacquire a mutex already held by the same work item. The input does not establish whether an attacker can trigger this, or specify network access, authentication, or user interaction requirements.
Engineers running Linux kernels with the affected USB Type-C DisplayPort code should check their versions against the vendor advisory; affected versions were not provided.