# CVE-2026-93039: ASoC: meson: Keep link pointers valid on realloc failure

> A use-after-free vulnerability in the Linux kernel's Meson audio driver allows attackers to potentially execute code or escalate privileges via a double free error during memory reallocation failures.

- **Severity:** High 7.4 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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-102126, BELL-CVE-2026-93039, DEBIAN-CVE-2026-93039, GHSA-w65f-8rhv-gqvr, UBUNTU-CVE-2026-93039

## What is CVE-2026-93039?

CVE-2026-93039 is a high-severity 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: meson: Keep link pointers valid on realloc failure

meson_card_reallocate_links() grows the DAI link and private data
arrays with two consecutive krealloc() calls and updates the owner
pointers only after both calls have succeeded.

A successful krealloc() may move the data: it frees the old block and
returns a new one. When that happens for the link array and the second
krealloc() then fails, card->dai_link still points to the block that
krealloc() already freed, and the error path frees the new block too.
The probe error path then calls meson_card_clean_references(), which
dereferences card->dai_link and kfree()s it again, resulting in a
use-after-free and a double free.

Commit card->dai_link and card->num_links right after the first
krealloc() succeeds, so the pointer always refers to a valid allocation
that meson_card_clean_references() can walk and free. krealloc() with
__GFP_ZERO zero-initializes the added entries, so walking them on the
error path is safe. With both failure paths reduced to a plain return,
drop the goto labels and the error message.

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


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

Apply the vendor's patch.

## Is CVE-2026-93039 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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