CVE-2026-23281
Description
In the Linux kernel, the following vulnerability has been resolved:
wifi: libertas: fix use-after-free in lbs_free_adapter()
The lbs_free_adapter() function uses timer_delete() (non-synchronous) for both command_timer and tx_lockup_timer before the structure is freed. This is incorrect because timer_delete() does not wait for any running timer callback to complete.
If a timer callback is executing when lbs_free_adapter() is called, the callback will access freed memory since lbs_cfg_free() frees the containing structure immediately after lbs_free_adapter() returns.
Both timer callbacks (lbs_cmd_timeout_handler and lbs_tx_lockup_handler) access priv->driver_lock, priv->cur_cmd, priv->dev, and other fields, which would all be use-after-free violations.
Use timer_delete_sync() instead to ensure any running timer callback has completed before returning.
This bug was introduced in commit 8f641d93c38a ("libertas: detect TX lockups and reset hardware") where del_timer() was used instead of del_timer_sync() in the cleanup path. The command_timer has had the same issue since the driver was first written.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Use-after-free in libertas wifi driver due to non-synchronous timer deletion; fixed by using timer_delete_sync().
Root Cause The lbs_free_adapter() function in the libertas WiFi driver used timer_delete() (non-synchronous) to cancel command_timer and tx_lockup_timer before freeing the containing structure via lbs_cfg_free(). Because timer_delete() does not wait for a running callback to finish, a concurrently executing timer callback could access freed memory, leading to a use-after-free vulnerability [1].
Exploitation An attacker able to trigger device removal (e.g., via hot-unplug or module removal) while either timer is executing can cause the callbacks lbs_cmd_timeout_handler or lbs_tx_lockup_handler to dereference freed pointers such as priv->driver_lock, priv->cur_cmd, or priv->dev. Local access or crafted wireless conditions may be required to align timer execution with deallocation [2].
Impact Successful exploitation results in a use-after-free condition, which can lead to memory corruption, denial of service, or potential privilege escalation in a kernel context [3].
Mitigation The fix replaces timer_delete() with timer_delete_sync(), ensuring any running timer callback completes before the structure is freed. The patch has been backported to stable kernel trees [4]. Users should apply the latest kernel updates to mitigate this vulnerability.
AI Insight generated on May 18, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
8- git.kernel.org/stable/c/03cc8f90d0537fcd4985c3319b4fafbf2e3fb1f0nvd
- git.kernel.org/stable/c/09f3c30ab3b1371eaf9676a1b8add57bca763083nvd
- git.kernel.org/stable/c/3c5c818c78b03a1725f3dcd566865c77b48dd3a6nvd
- git.kernel.org/stable/c/3f9dec4a6d95d7f1f5e9e9dfdfa173c053bba8dcnvd
- git.kernel.org/stable/c/a9f55b14486426d907459bced5825a25063bd922nvd
- git.kernel.org/stable/c/b15e0fa7adb4de3a03aee9e6fc4d83e5cf0a65e4nvd
- git.kernel.org/stable/c/d0155fe68f31b339961cf2d4f92937d57e9384e6nvd
- git.kernel.org/stable/c/ed7d30f90b77f73a47498686ede83f622b7e4f0dnvd
News mentions
0No linked articles in our index yet.