CVE-2026-23281

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: libertas: fix use-after-free in lbs_free_adapter()<br /> <br /> The lbs_free_adapter() function uses timer_delete() (non-synchronous)<br /> for both command_timer and tx_lockup_timer before the structure is<br /> freed. This is incorrect because timer_delete() does not wait for<br /> any running timer callback to complete.<br /> <br /> If a timer callback is executing when lbs_free_adapter() is called,<br /> the callback will access freed memory since lbs_cfg_free() frees the<br /> containing structure immediately after lbs_free_adapter() returns.<br /> <br /> Both timer callbacks (lbs_cmd_timeout_handler and lbs_tx_lockup_handler)<br /> access priv-&gt;driver_lock, priv-&gt;cur_cmd, priv-&gt;dev, and other fields,<br /> which would all be use-after-free violations.<br /> <br /> Use timer_delete_sync() instead to ensure any running timer callback<br /> has completed before returning.<br /> <br /> This bug was introduced in commit 8f641d93c38a ("libertas: detect TX<br /> lockups and reset hardware") where del_timer() was used instead of<br /> del_timer_sync() in the cleanup path. The command_timer has had the<br /> same issue since the driver was first written.