CVE-2025-38505
BaseFortify
Publication date: 2025-08-16
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 | 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) |
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 occurs in the Linux kernel's mwifiex driver when operating in concurrent STA/AP mode with host MLME enabled. The firmware incorrectly sends disassociation frames to the STA interface when clients disconnect from the AP interface. These erroneous frames cause kernel warnings because the STA interface processes disconnect events that do not apply to it. The issue is fixed by adding validation to ensure that disassociation and deauthentication frames are only accepted if they originate from the connected AP, discarding irrelevant frames early to prevent kernel warnings.
How can this vulnerability impact me? :
This vulnerability can cause kernel warnings and instability in the wireless networking stack by processing incorrect disconnect events on the STA interface. While it does not directly cause security breaches, it may lead to system instability or degraded wireless performance due to improper handling of disassociation frames.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring kernel logs for warnings related to disassociation frames on the STA interface. Specifically, look for kernel warning messages similar to: "WARNING: CPU: ... at net/wireless/mlme.c:141 cfg80211_process_disassoc". You can use the command 'dmesg | grep cfg80211_process_disassoc' or 'journalctl -k | grep cfg80211_process_disassoc' to find such warnings in the system 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. The fix discards erroneous disassociation frames on the STA interface by validating that such frames originate from the connected AP, preventing kernel warnings and potential issues. Until the update is applied, monitoring logs for the warning and avoiding concurrent STA/AP mode with host MLME enabled may reduce exposure.