Описание
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:
- cros_typec_altmode_work() acquires the mutex
- typec_altmode_vdm() -> dp_altmode_vdm() ->
- typec_altmode_exit() -> cros_typec_altmode_exit()
- 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.
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:
- cros_typec_altmode_work() acquires the mutex
- typec_altmode_vdm() -> dp_altmode_vdm() ->
- typec_altmode_exit() -> cros_typec_altmode_exit()
- 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.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2025-38404
- https://git.kernel.org/stable/c/099cf1fbb8afc3771f408109f62bdec66f85160e
- https://git.kernel.org/stable/c/63cff9f57e86b2dc25d7487ca0118df89a665296
- https://git.kernel.org/stable/c/749d9076735fb497aae60fbea9fff563f9ea3254
- https://git.kernel.org/stable/c/76cf1f33e7319fe74c94ac92f9814094ee8cc84b
- https://git.kernel.org/stable/c/7be0d1ea71f52595499da39cea484a895e8ed042
- https://git.kernel.org/stable/c/80c25d7916a44715338d4f8924c8e52af50d0b9f
- https://git.kernel.org/stable/c/c782f98eef14197affa8a7b91e6981420f109ea9
- https://git.kernel.org/stable/c/eb08fca56f1f39e4038cb9bac9864464b13b00aa
EPSS
CVE ID
Связанные уязвимости
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.
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.
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.
In the Linux kernel, the following vulnerability has been resolved: u ...
EPSS