CVE-2025-39891
What it is
In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: Initialize the chan_stats array to zero The adapter->chan_stats[] array is initialized in mwifiex_init_channel_scan_gap() with vmalloc(), which doesn't zero out memory. The array is filled in mwifiex_update_chan_statistics() and then the user can query the data in mwifiex_cfg80211_dump_survey(). There are two potential issues here. What if the user calls mwifiex_cfg80211_dump_survey() before the data has been filled in. Also the mwifiex_update_chan_statistics() function doesn't necessarily initialize the whole array. Since the array was not initialized at the start that could result in an information leak. Also this array is pretty small. It's a maximum of 900 bytes so it's more appropriate to use kcalloc() instead vmalloc().
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.1 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Analyzed
Affected
- Linux Kernel < 5.4.299
- Linux Kernel < 5.10.243
- Linux Kernel < 5.15.192
- Linux Kernel < 6.1.151
- Linux Kernel < 6.6.105
- Linux Kernel < 6.12.46
- Linux Kernel < 6.16.6
- Linux Kernel 6.17
Attack profile CVSS 3.1 · 7.1
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-39891.md and follow it. Check whether this project is affected by CVE-2025-39891. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/05daef0442d28350a1a0d6d0e2cab4a7a91df475
- https://git.kernel.org/stable/c/06616410a3e5e6cd1de5b7cbc668f1a7edeedad9
- https://git.kernel.org/stable/c/0e20450829ca3c1dbc2db536391537c57a40fe0b
- https://git.kernel.org/stable/c/32c124c9c03aa755cbaf60ef7f76afd918d47659
- https://git.kernel.org/stable/c/5285b7009dc1e09d5bb9e05fae82e1a807882dbc
- https://git.kernel.org/stable/c/9df29aa5637d94d24f7c5f054ef4feaa7b766111
- https://git.kernel.org/stable/c/9eb0118b3470b4d2e4e3bbb1fc088b30c0285d65
- https://git.kernel.org/stable/c/acdf26a912190fc6746e2a890d7d0338190527b4
References
- https://git.kernel.org/stable/c/05daef0442d28350a1a0d6d0e2cab4a7a91df475
- https://git.kernel.org/stable/c/06616410a3e5e6cd1de5b7cbc668f1a7edeedad9
- https://git.kernel.org/stable/c/0e20450829ca3c1dbc2db536391537c57a40fe0b
- https://git.kernel.org/stable/c/32c124c9c03aa755cbaf60ef7f76afd918d47659
- https://git.kernel.org/stable/c/5285b7009dc1e09d5bb9e05fae82e1a807882dbc
- https://git.kernel.org/stable/c/9df29aa5637d94d24f7c5f054ef4feaa7b766111
- https://git.kernel.org/stable/c/9eb0118b3470b4d2e4e3bbb1fc088b30c0285d65
- https://git.kernel.org/stable/c/acdf26a912190fc6746e2a890d7d0338190527b4
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html