CVE-2025-38174
BaseFortify
Publication date: 2025-07-04
Last updated on: 2025-12-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 3.17 (inc) to 5.4.295 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.239 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.186 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.142 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.6.94 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.33 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.14.11 (exc) |
| linux | linux_kernel | From 6.15 (inc) to 6.15.2 (exc) |
| debian | debian_linux | 11.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel's Thunderbolt driver involves a flaw where a configuration request can be dequeued twice. Specifically, the function tb_cfg_request_dequeue() may be called twice for the same request due to it being scheduled twice via different paths. This double dequeue leads to a double removal from a request queue, causing a crash with a general protection fault due to accessing invalid memory addresses.
How can this vulnerability impact me? :
The vulnerability can cause devices using the affected Linux kernel Thunderbolt driver to crash unexpectedly. This crash results from a general protection fault triggered by double dequeuing configuration requests, potentially leading to system instability or denial of service.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring system logs for crashes related to the thunderbolt configuration request dequeue process. Specifically, look for kernel messages indicating a general protection fault in tb_cfg_request_dequeue, such as logs containing 'general protection fault', 'tb_cfg_request_dequeue', or addresses like '0xdead000000000122'. Commands like 'dmesg | grep tb_cfg_request_dequeue' or 'journalctl -k | grep tb_cfg_request_dequeue' can help identify these crash logs.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this vulnerability is resolved, as the issue is fixed by preventing double dequeue of configuration requests in the thunderbolt driver. Until an update is applied, avoid workloads or configurations that trigger thunderbolt configuration requests heavily, and monitor for related crashes to minimize impact.