https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 23:59:42 +0000 https://vulnerability.circl.lu/vuln/cve-2026-46069 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>wifi: mwifiex: fix use-after-free in mwifiex_adapter_cleanup()</p> <p>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.</p> <p>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-&gt;hw_status, adapter-&gt;if_ops.card_reset, etc.) which may be freed by mwifiex_free_adapter() called later in the mwifiex_remove_card() path.</p> <p>Use timer_delete_sync() instead to ensure any running timer callback has completed before returning.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>wifi: mwifiex: fix use-after-free in mwifiex_adapter_cleanup()</p> <p>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.</p> <p>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-&gt;hw_status, adapter-&gt;if_ops.card_reset, etc.) which may be freed by mwifiex_free_adapter() called later in the mwifiex_remove_card() path.</p> <p>Use timer_delete_sync() instead to ensure any running timer callback has completed before returning.</p> https://vulnerability.circl.lu/vuln/cve-2026-46069