Skip to main content
VulnerabilityPublished Updated

CVE-2026-46069: Linux kernel · wifi: mwifiex: fix use-after-free in mwifiex_adapter_cleanup()

Affects Linux kernelSource CVE Database V5

0
Compare

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

Data as of 6 Nov 2026, 16:34 UTC

Severity
Unrated

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

Thin evidence

One scorer or none
CISA SSVC
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-06.

Patch
Available – fixed in c3508895450cca4aeaf5dbadbb5e582363005264, ae5e95d4157481693be2317e3ffcd84e36010cbb, a88f5391dc68f78cae5eb6a8cd341cafee795d3d +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 4636187da60b6e33526050235c610409d9cc00e8, < c3508895450cca4aeaf5dbadbb5e582363005264
Fixed in
  • c3508895450cca4aeaf5dbadbb5e582363005264
LinuxLinuxAffected
  • ≥ 4636187da60b6e33526050235c610409d9cc00e8, < ae5e95d4157481693be2317e3ffcd84e36010cbb
Fixed in
  • ae5e95d4157481693be2317e3ffcd84e36010cbb
LinuxLinuxAffected
  • ≥ 4636187da60b6e33526050235c610409d9cc00e8, < a88f5391dc68f78cae5eb6a8cd341cafee795d3d
Fixed in
  • a88f5391dc68f78cae5eb6a8cd341cafee795d3d
LinuxLinuxAffected
  • ≥ 4636187da60b6e33526050235c610409d9cc00e8, < 11869ce402d95519d49b25a2a97741f68d69d103
Fixed in
  • 11869ce402d95519d49b25a2a97741f68d69d103
LinuxLinuxAffected
  • ≥ 4636187da60b6e33526050235c610409d9cc00e8, < 1958a92599b2653d730ccb6f5685fc3fbed21812
Fixed in
  • 1958a92599b2653d730ccb6f5685fc3fbed21812
LinuxLinuxAffected
  • ≥ 4636187da60b6e33526050235c610409d9cc00e8, < 63fe3389b3e092d6c0eeea9fc0318e7918b16618
Fixed in
  • 63fe3389b3e092d6c0eeea9fc0318e7918b16618

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: fix use-after-free in mwifiex_adapter_cleanup() The mwifiex_adapter_cleanup() function uses timer_delete() (non-synchronous) for the wakeup_timer before the adapter structure is freed. This is incorrect because timer_delete() does not wait for any running timer callback to complete. If the wakeup_timer callback (wakeup_timer_fn) is executing when mwifiex_adapter_cleanup() is called, the callback will continue to access adapter fields (adapter->hw_status, adapter->if_ops.card_reset, etc.) which may be freed by mwifiex_free_adapter() called later in the mwifiex_remove_card() path. Use timer_delete_sync() instead to ensure any running timer callback has completed before returning.

References

Community reviews

Loading reviews…