CVE-2025-39891In 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_…
Updated under an hour ago ()
Does this affect you?
It affects linux_kernel and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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().
- CVSS
- 7.1 HIGH (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Not given
- NVD analysis
- Analyzed
- Record last updated
- Oct 19, 2026
- First seen by InfoSec Signals
- Oct 19, 2026
Affected products
linux linux_kernel linux:linux_kernel | from 3.19 before 5.4.299; from 5.5 before 5.10.243; from 5.11 before 5.15.192; from 5.16 before 6.1.151; from 6.2 before 6.6.105; from 6.7 before 6.12.46; from 6.13 before 6.16.6; 6.17; and 3 more ranges | NVD |
debian debian_linux debian:debian_linux | 11.0 | NVD |
References
- https://git.kernel.org/stable/c/05daef0442d28350a1a0d6d0e2cab4a7a91df475patch
- https://git.kernel.org/stable/c/06616410a3e5e6cd1de5b7cbc668f1a7edeedad9patch
- https://git.kernel.org/stable/c/0e20450829ca3c1dbc2db536391537c57a40fe0bpatch
- https://git.kernel.org/stable/c/32c124c9c03aa755cbaf60ef7f76afd918d47659patch
- https://git.kernel.org/stable/c/5285b7009dc1e09d5bb9e05fae82e1a807882dbcpatch
- https://git.kernel.org/stable/c/9df29aa5637d94d24f7c5f054ef4feaa7b766111patch
- https://git.kernel.org/stable/c/9eb0118b3470b4d2e4e3bbb1fc088b30c0285d65patch
- https://git.kernel.org/stable/c/acdf26a912190fc6746e2a890d7d0338190527b4patch
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.htmlmailing-list, third-party-advisory
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.htmlmailing-list, third-party-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.