# CVE-2026-90214: ASoC: xilinx: formatter_pcm: fix stream_data leak on open error

> A use-after-free vulnerability in the Linux kernel's Xilinx formatter PCM driver allows local attackers to execute arbitrary code or cause a denial of service via a specific error path during stream opening.

- **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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102305, BELL-CVE-2026-90214, DEBIAN-CVE-2026-90214, GHSA-2gxq-r2mx-5g9g, UBUNTU-CVE-2026-90214

## What is CVE-2026-90214?

CVE-2026-90214 is an use after free vulnerability in Linux, published on 17 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: xilinx: formatter_pcm: fix stream_data leak on open error

In xlnx_formatter_pcm_open(), stream_data is allocated and
adata->play_stream or adata->capture_stream is assigned early.  If a
later step, such as snd_pcm_hw_constraint_step() or
snd_pcm_hw_constraint_integer(), fails, the function returns the error
immediately.  ALSA does not call the close callback when open fails, so
stream_data is leaked and the stream pointer is left dangling, pointing
to a substream that ALSA frees.  A later interrupt would then call
snd_pcm_period_elapsed() on the freed substream.

Free stream_data and clear the stream pointer on the error paths.

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


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

Apply the vendor's patch.

## Is CVE-2026-90214 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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