CVE-2026-72070

wifi: libertas_tf: fix use-after-free in lbtf_free_adapter()

N/A
Published: August 15, 2026 at 05:52 AM UTC
Updated: August 23, 2026 at 01:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: libertas_tf: fix use-after-free in lbtf_free_adapter() lbtf_free_adapter() calls timer_delete(&priv->command_timer), which does not wait for a running command_timer_fn() callback. lbtf_free_adapter() runs on the teardown path right before ieee80211_free_hw() frees priv, both in lbtf_remove_card() and in the probe error path. command_timer is armed by mod_timer() in lbtf_cmd() whenever a firmware command is sent. command_timer_fn() dereferences priv. If a command times out as the device is removed, command_timer_fn() runs concurrently with teardown and dereferences priv after it has been freed. This is the same use-after-free that commit 03cc8f90d053 ("wifi: libertas: fix use-after-free in lbs_free_adapter()") fixed in the sibling libertas driver. The libertas_tf variant has the identical pattern and was left unchanged. Use timer_delete_sync() so any in-flight callback completes before priv is freed.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.28 ≤ v < 5.10.2662.6.28 ≤ v < 5.15.2172.6.28 ≤ v < 6.1.1842.6.28 ≤ v < 6.12.1012.6.28 ≤ v < 6.18.402.6.28 ≤ v < 6.6.1482.6.28 ≤ v < 7.1.52.6.28 ≤ v < 7.22.6.286b16ae5319251c26377afcb401e46056d5673f4
Vendor states this is fixed in 066b59e84f90d270cc15f0370166155aca507630 (fixed)
Vendor states this is fixed in 2fba1d3b2f031a2c68e566a6d45cc5b7a8d6683d (fixed)
Vendor states this is fixed in 4714e95f5d61cb9c5c7c6c4e68b618f37bc6ffcf (fixed)
Vendor states this is fixed in 9392fd5de555272449d3d8c63410ea00f8ec853a (fixed)
Vendor states this is fixed in aa6dcd5c8dd9ba1d7d0f60093bcda41c0d6d438d (fixed)
Vendor states this is fixed in bcf7968cb97ce4312588042cf2712f04caff6d8f (fixed)
Vendor states this is fixed in bd75636681588c67006279abdb9a76a708b3ce29 (fixed)
Vendor states this is fixed in fcff712d0e3d183843ec3916470ee6cc3455baad (fixed)
Vendor states this is fixed in 2.6.28 (unaffected)
Vendor states this is fixed in 5.10.266 (unaffected)
Vendor states this is fixed in 5.15.217 (unaffected)
Vendor states this is fixed in 6.1.184 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card