CVE-2025-38379
BaseFortify
Publication date: 2025-07-25
Last updated on: 2025-11-19
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
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 is related to the Linux kernel's SMB client implementation. When reconnecting a channel in the smb2_reconnect_server() function, a dummy tcon (tree connection) is passed to smb2_reconnect() with its query_interface field uninitialized. This causes a warning because the system attempts to call queue_delayed_work() on an uninitialized structure. The fix ensures that the delayed work is queued from the correct tcon, preventing this warning and potential instability.
How can this vulnerability impact me? :
This vulnerability can cause warnings and potentially unstable behavior in the Linux kernel when reconnecting SMB channels, which may affect system stability or reliability when using SMB client features. However, there is no indication that it leads to security breaches such as data loss or unauthorized access.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability manifests as a kernel warning related to smb2_reconnect_server() and queue_delayed_work(). Detection involves monitoring the system kernel logs for warnings similar to: "WARNING: CPU: ... at kernel/workqueue.c:2498 __queue_delayed_work" and messages referencing smb2_reconnect_server or cifs modules. You can check kernel logs using commands like: dmesg | grep -i 'queue_delayed_work' or journalctl -k | grep -i 'smb2_reconnect_server'.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this issue is fixed, as the vulnerability is resolved by correcting the handling of delayed work in smb2_reconnect_server(). Until an update is applied, monitoring kernel logs for the warning can help identify if the issue occurs. There are no specific configuration changes or workarounds detailed.