# CVE-2026-80911: ASoC: SOF: sof-audio: Fix error path in sof_widget_setup_unlocked()

> A double decrement of use_count in the Linux kernel SOF audio driver can lead to a use-after-free condition, potentially causing a system crash.

- **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-99470, BELL-CVE-2026-80911, DEBIAN-CVE-2026-80911, GHSA-v4fw-33v9-5mm7, UBUNTU-CVE-2026-80911

## What is CVE-2026-80911?

CVE-2026-80911 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:

ASoC: SOF: sof-audio: Fix error path in sof_widget_setup_unlocked()

If either tplg_ops->dai_config or widget_kcontrol_setup fail during widget
setup we would double decrement the use_count of the widget because the
sof_widget_free_unlocked() would be called twice, similarly the core_put
would be invoked twice as well.

Since the use_count and core_put() is handled within the widget_free
function we need to return without falling through the pipe_widget_free
label.

The fixes tag is picked to the last change around this part of the code
which is adequately old enough for backporting purposes.

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


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

Apply the vendor's patch.

## Is CVE-2026-80911 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80911 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-80911 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-80911/ (Markdown: https://insights.sbomify.com/CVE-2026-80911/index.md)
```

## Sources

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

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