CVE-2025-38404
published 2025-07-25CVE-2025-38404: In the Linux kernel, the following vulnerability has been resolved: usb: typec: displayport: Fix potential deadlock The deadlock can occur due to a recursive…
PriorityP418medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.13%
3.0th percentile
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.
Affected
26 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | linux | < linux 6.1.147-1 (bookworm) | linux 6.1.147-1 (bookworm) |
| debian | linux-6.1 | < linux 6.1.147-1 (bookworm) | linux 6.1.147-1 (bookworm) |
| linux | linux | >= 10cc2cfd3e5d0e0ec7590c4bee8bcea10e5492c4 < c782f98eef14197affa8a7b91e6981420f109ea9 | c782f98eef14197affa8a7b91e6981420f109ea9 |
| linux | linux | >= 56846793f105cf2b39ecbde4f3ae86342091f6fc < 7be0d1ea71f52595499da39cea484a895e8ed042 | 7be0d1ea71f52595499da39cea484a895e8ed042 |
| linux | linux | >= 6.1.143 < 6.1.144 | 6.1.144 |
| linux | linux | >= 6.12.36 < 6.12.37 | 6.12.37 |
| linux | linux | >= 6.15.5 < 6.15.6 | 6.15.6 |
| linux | linux | >= 6.6.96 < 6.6.97 | 6.6.97 |
| linux | linux | >= 8851e40587013db00b71d4aeaae30f5fd59b0eec < 63cff9f57e86b2dc25d7487ca0118df89a665296 | 63cff9f57e86b2dc25d7487ca0118df89a665296 |
| linux | linux | >= 8e8a69b1f8c59f0505f8a1c0fb77191f27b75011 < 76cf1f33e7319fe74c94ac92f9814094ee8cc84b | 76cf1f33e7319fe74c94ac92f9814094ee8cc84b |
| linux | linux | >= 8f6a4fa7b663468bb304cb885b93326e025ae005 < 80c25d7916a44715338d4f8924c8e52af50d0b9f | 80c25d7916a44715338d4f8924c8e52af50d0b9f |
| linux | linux | >= b4b38ffb38c91afd4dc387608db26f6fc34ed40b < 099cf1fbb8afc3771f408109f62bdec66f85160e | 099cf1fbb8afc3771f408109f62bdec66f85160e |
| linux | linux | >= e0359c66c1beccbe90119a63391678eabda38007 < 749d9076735fb497aae60fbea9fff563f9ea3254 | 749d9076735fb497aae60fbea9fff563f9ea3254 |
| linux | linux | >= e3fb6c2c3939b4aad203cacdd613a62ce1fd032c < eb08fca56f1f39e4038cb9bac9864464b13b00aa | eb08fca56f1f39e4038cb9bac9864464b13b00aa |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.244-1 | 5.10.244-1 |
| linux | linux_kernel | >= 0 < 6.1.147-1 | 6.1.147-1 |
| linux | linux_kernel | >= 0 < 6.12.37-1 | 6.12.37-1 |
| linux | linux_kernel | >= 0 < 6.12.37-1 | 6.12.37-1 |
| msrc | azl3_kernel_6.6.96.2-1_on_azure_linux_3.0 | — | — |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_msrc5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: usb: typec: displayport: Fix potential deadlock
vendor_redhat·2025-07-25·CVSS 5.5
CVE-2025-38404 [MEDIUM] kernel: usb: typec: displayport: Fix potential deadlock
kernel: usb: typec: displayport: Fix potential deadlock
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.
Package: kernel (Red Hat Enterprise Linux 10) - Not affected
Package: kernel (Red Hat Enterprise Linux 6) - Not affected
Package: kernel (Red
Microsoft
usb: typec: displayport: Fix potential deadlock
vendor_msrc·2025-07-08·CVSS 5.5
CVE-2025-38404 [MEDIUM] usb: typec: displayport: Fix potential deadlock
usb: typec: displayport: Fix potential deadlock
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information. If impact to additional products is identified, we will update the CVE to reflect this.
Mariner: Mariner
Linux: Linux
Customer Action Required: Yes
Remediation: CBL-Mariner Releases
Reference: https://learn.microso
Debian
CVE-2025-38404: linux - In the Linux kernel, the following vulnerability has been resolved: usb: typec:...
vendor_debian·2025·CVSS 5.5
CVE-2025-38404 [MEDIUM] CVE-2025-38404: linux - In the Linux kernel, the following vulnerability has been resolved: usb: typec:...
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.
Scope: local
bookworm: resolved (fixed in 6.1.147-1)
bullseye: resolved (fixed in 5.10.244-1)
forky: resolved (fixed in 6.12.37-1)
sid: resolved (fixed in 6.12.37-1)
trixie: resolved (fixed in 6.12.37-
OSV
CVE-2025-38404: In the Linux kernel, the following vulnerability has been resolved: usb: typec: displayport: Fix potential deadlock The deadlock can occur due to a re
osv·2025-07-25·CVSS 5.5
CVE-2025-38404 [MEDIUM] CVE-2025-38404: In the Linux kernel, the following vulnerability has been resolved: usb: typec: displayport: Fix potential deadlock The deadlock can occur due to a re
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.
GHSA
GHSA-whrv-p2hp-qr7f: In the Linux kernel, the following vulnerability has been resolved:
usb: typec: displayport: Fix potential deadlock
The deadlock can occur due to a
ghsa_unreviewed·2025-07-25
CVE-2025-38404 [MEDIUM] CWE-667 GHSA-whrv-p2hp-qr7f: In the Linux kernel, the following vulnerability has been resolved:
usb: typec: displayport: Fix potential deadlock
The deadlock can occur due to a
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.
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/099cf1fbb8afc3771f408109f62bdec66f85160ehttps://git.kernel.org/stable/c/63cff9f57e86b2dc25d7487ca0118df89a665296https://git.kernel.org/stable/c/749d9076735fb497aae60fbea9fff563f9ea3254https://git.kernel.org/stable/c/76cf1f33e7319fe74c94ac92f9814094ee8cc84bhttps://git.kernel.org/stable/c/7be0d1ea71f52595499da39cea484a895e8ed042https://git.kernel.org/stable/c/80c25d7916a44715338d4f8924c8e52af50d0b9fhttps://git.kernel.org/stable/c/c782f98eef14197affa8a7b91e6981420f109ea9https://git.kernel.org/stable/c/eb08fca56f1f39e4038cb9bac9864464b13b00aahttps://lists.debian.org/debian-lts-announce/2025/10/msg00007.htmlhttps://lists.debian.org/debian-lts-announce/2025/10/msg00008.html
2025-07-25
Published