CVE Catalog

CVE-2026-23281

HighCVSS 7.8
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.13%

2th percentile - higher than 2% of all known CVEs

Summary

In the Linux kernel, the libertas wifi driver function lbs_free_adapter() uses timer_delete() instead of timer_delete_sync(), which does not wait for running timer callbacks to complete. This leads to a use-after-free because callbacks (lbs_cmd_timeout_handler and lbs_tx_lockup_handler) may access freed memory.

Risk Assessment

A use-after-free in the kernel may cause system crashes, memory corruption, or potential code execution. It affects systems using Wi-Fi devices based on the libertas driver.

Recommendation

Update the Linux kernel to a version containing the fix that replaces timer_delete() with timer_delete_sync(). If updating is not possible, consider disabling or restricting use of affected Wi-Fi devices.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS