VulnerabilityPublished 1 Oct 2025Updated 5 Nov 2026

CVE-2025-39891: Linux kernel · wifi: mwifiex: Initialize the chan_stats array to zero

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in acdf26a912190fc6746e2a890d7d0338190527b4 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:49 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch

Available – fixed in acdf26a912190fc6746e2a890d7d0338190527b4, 06616410a3e5e6cd1de5b7cbc668f1a7edeedad9, 5285b7009dc1e09d5bb9e05fae82e1a807882dbc +5

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ bf35443314acb43fa8a3f9f8046e14cbe178762b, < acdf26a912190fc6746e2a890d7d0338190527b4	Fixed in acdf26a912190fc6746e2a890d7d0338190527b4
LinuxLinux	Affected ≥ bf35443314acb43fa8a3f9f8046e14cbe178762b, < 06616410a3e5e6cd1de5b7cbc668f1a7edeedad9	Fixed in 06616410a3e5e6cd1de5b7cbc668f1a7edeedad9
LinuxLinux	Affected ≥ bf35443314acb43fa8a3f9f8046e14cbe178762b, < 5285b7009dc1e09d5bb9e05fae82e1a807882dbc	Fixed in 5285b7009dc1e09d5bb9e05fae82e1a807882dbc
LinuxLinux	Affected ≥ bf35443314acb43fa8a3f9f8046e14cbe178762b, < 32c124c9c03aa755cbaf60ef7f76afd918d47659	Fixed in 32c124c9c03aa755cbaf60ef7f76afd918d47659
LinuxLinux	Affected ≥ bf35443314acb43fa8a3f9f8046e14cbe178762b, < 9eb0118b3470b4d2e4e3bbb1fc088b30c0285d65	Fixed in 9eb0118b3470b4d2e4e3bbb1fc088b30c0285d65
LinuxLinux	Affected ≥ bf35443314acb43fa8a3f9f8046e14cbe178762b, < 9df29aa5637d94d24f7c5f054ef4feaa7b766111	Fixed in 9df29aa5637d94d24f7c5f054ef4feaa7b766111

Description

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().

References

Community reviews

Loading reviews…