CVE-2025-38268
BaseFortify
Publication date: 2025-07-10
Last updated on: 2025-11-20
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | 6.9 |
| linux | linux_kernel | 6.9 |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-667 | The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel's USB Type-C TCPM (Type-C Port Manager) involves a deadlock issue caused by improper locking and state checking in the handling of DisplayPort Alternate Mode. Specifically, a state check in the function tcpm_queue_vdm_unlocked was not properly protected, allowing a small timing window where the Alt Mode driver and TCPM could both attempt to acquire locks in a way that leads to a deadlock. This deadlock occurs when the DisplayPort Alt Mode driver tries to grab the TCPM lock while TCPM is holding the lock and attempting to unregister the altmode, causing the system to block indefinitely. The fix involved moving the function to asynchronous work and restructuring the locking to prevent this deadlock.
How can this vulnerability impact me? :
This vulnerability can cause a deadlock in the Linux kernel's USB Type-C port management, potentially leading to system hangs or freezes when handling DisplayPort Alternate Mode connections. This can disrupt normal device operation, causing loss of functionality or requiring a system reboot to recover, which impacts system stability and availability.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version that includes the fix where tcpm_queue_vdm_unlocked is moved to asynchronous work, preventing the deadlock condition. This involves applying the patch that changes the queuing mechanism to avoid holding conflicting locks simultaneously.