wifi: libertas: fix use-after-free in lbs_free_adapter()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 954ee164f4f4598afc172c0ec3865d0352e55a0b · fixed in b15e0fa7adb4de3a03aee9e6fc4d83e5cf0a65e4; From 954ee164f4f4598afc172c0ec3865d0352e55a0b · fixed in 09f3c30ab3b1371eaf9676a1b8add57bca763083; From 954ee164f4f4598afc172c0ec3865d0352e55a0b · fixed in 3f9dec4a6d95d7f1f5e9e9dfdfa173c053bba8dc; From 954ee164f4f4598afc172c0ec3865d0352e55a0b · fixed in 3c5c818c78b03a1725f3dcd566865c77b48dd3a6; From 954ee164f4f4598afc172c0ec3865d0352e55a0b · fixed in d0155fe68f31b339961cf2d4f92937d57e9384e6; From 954ee164f4f4598afc172c0ec3865d0352e55a0b · fixed in ed7d30f90b77f73a47498686ede83f622b7e4f0d; From 954ee164f4f4598afc172c0ec3865d0352e55a0b · fixed in a9f55b14486426d907459bced5825a25063bd922; From 954ee164f4f4598afc172c0ec3865d0352e55a0b · fixed in 03cc8f90d0537fcd4985c3319b4fafbf2e3fb1f0
- Linux Linux
2.6.24
- KernelLinux
From 2.6.24 · fixed in 5.10.253; From 5.11.0 · fixed in 5.15.203; From 5.16.0 · fixed in 6.1.167; From 6.2.0 · fixed in 6.6.130; From 6.7.0 · fixed in 6.12.78; From 6.13.0 · fixed in 6.18.17; From 6.19.0 · fixed in 6.19.7
References 8
git.kernel.org
- stable/c/b15e0fa7adb4de3a03aee9e6fc4d83e5cf0a65e4
- stable/c/09f3c30ab3b1371eaf9676a1b8add57bca763083
- stable/c/3f9dec4a6d95d7f1f5e9e9dfdfa173c053bba8dc
- stable/c/3c5c818c78b03a1725f3dcd566865c77b48dd3a6
- stable/c/d0155fe68f31b339961cf2d4f92937d57e9384e6
- stable/c/ed7d30f90b77f73a47498686ede83f622b7e4f0d
- stable/c/a9f55b14486426d907459bced5825a25063bd922
- stable/c/03cc8f90d0537fcd4985c3319b4fafbf2e3fb1f0