# CVE-2026-80872: ALSA: hda/tas2781: Cancel async firmware request at unbind

> A race condition in the TAS2781 HDA driver allows use-after-free during device unbind, potentially causing system crashes or code execution.

- **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:** 4 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** AZL-99489, BELL-CVE-2026-80872, DEBIAN-CVE-2026-80872, GHSA-cwhx-gq4m-wm56, UBUNTU-CVE-2026-80872

## What is CVE-2026-80872?

CVE-2026-80872 is an use after free vulnerability in Linux, published on 4 Sep 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:

ALSA: hda/tas2781: Cancel async firmware request at unbind

TAS2781 HDA I2C and SPI queue RCA firmware loading from component
bind with request_firmware_nowait(). The firmware loader keeps the
callback module pinned and holds a device reference, but the callback
still uses driver-private HDA state.

Component unbind removes controls and DSP state immediately. Later
device removal tears down the TAS2781 private data, including
codec_lock. If the async firmware callback runs after unbind has
started, it can operate on state that is being torn down.

Cancel or synchronize the async firmware request before removing
controls and DSP state. A queued callback is cancelled, and an
already-running callback is allowed to finish before unbind continues.

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


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

Apply the vendor's patch.

## Is CVE-2026-80872 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80872 is an use after free vulnerability in Linux, published on 4 Sep 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-80872 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-80872/ (Markdown: https://insights.sbomify.com/CVE-2026-80872/index.md)
```

## Sources

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

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