# CVE-2026-72070: wifi: libertas_tf: fix use-after-free in lbtf_free_adapter()

> A use-after-free in the Linux libertas_tf Wi-Fi driver allows attackers to cause denial of service or execute code during device teardown.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 23 Aug 2026
- **Also known as:** BELL-CVE-2026-72070, DEBIAN-CVE-2026-72070, GHSA-7vh5-jw3c-f9r7, UBUNTU-CVE-2026-72070

## What is CVE-2026-72070?

CVE-2026-72070 is an use after free vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-72070?


## How do I fix CVE-2026-72070?

Apply the vendor's patch.

## Is CVE-2026-72070 being exploited?

There is no known exploitation of CVE-2026-72070 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72070 and fix it if it is affected.

What it is: CVE-2026-72070 is an use after free vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72070 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72070/ (Markdown: https://insights.sbomify.com/CVE-2026-72070/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72070
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72070
- OSV: https://osv.dev/vulnerability/CVE-2026-72070

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72070/
Summaries are generated and may contain mistakes; the official description above is the record.
