CVE-2025-38291
BaseFortify
Publication date: 2025-07-10
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 | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-670 | The code contains a control flow path that does not reflect the algorithm that the path is intended to implement, leading to incorrect behavior any time this path is navigated. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's ath12k WiFi driver where WMI commands are sent to the firmware during a firmware crash and recovery phase. Sending these commands while the firmware is recovering causes the commands to fail and results in a kernel call trace (a type of error or crash log). The fix involves setting specific flags (ATH12K_FLAG_CRASH_FLUSH and ATH12K_FLAG_RECOVERY) when a firmware crash notification is received, which prevents sending WMI commands during firmware recovery.
How can this vulnerability impact me? :
This vulnerability can cause kernel call traces or crashes in the Linux kernel when the WiFi firmware crashes and the host continues to send commands during recovery. This can lead to system instability or degraded WiFi functionality until the issue is resolved.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing kernel call traces indicating firmware crashes related to the ath12k driver. Specifically, look for call traces involving ath12k_ce_send, ath12k_wmi_cmd_send, and related functions during firmware recovery. Monitoring kernel logs (e.g., using dmesg or journalctl) for such traces can help detect the issue. Example commands to check kernel logs include: 'dmesg | grep ath12k' or 'journalctl -k | grep ath12k'.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version where the fix is applied. The fix prevents sending WMI commands to the firmware during firmware crash recovery by setting ATH12K_FLAG_CRASH_FLUSH and ATH12K_FLAG_RECOVERY flags when a firmware crash notification is received. Until the update is applied, avoid actions that may trigger firmware crashes or WMI commands during recovery.