# CVE-2026-99068: ALSA: ctxfi: Fix memory leakage when clearing DAO input mappers


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** BELL-CVE-2026-99068, DEBIAN-CVE-2026-99068, GHSA-8467-wmq7-xf7q, UBUNTU-CVE-2026-99068

## What is CVE-2026-99068?

CVE-2026-99068 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

ALSA: ctxfi: Fix memory leakage when clearing DAO input mappers

Commit e576e7843c0d ("ALSA: ctxfi: Simplify dao_clear_{left,right}_input() functions")
centralized the DAO input mapper clearing logic in
dao_clear_input(), but omitted the kfree() calls.

It removes the mapper entries from the list and sets their pointers
to NULL without freeing the allocated array. This leaks memory each
time dao_clear_input() is called.

Store the base pointer of the allocation before clearing the mapper
entries and free the array after removing entries from the list.

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


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

Upgrade to a fixed version.

## Is CVE-2026-99068 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-99068 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99068 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-99068/ (Markdown: https://insights.sbomify.com/CVE-2026-99068/index.md)
```

## Sources

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

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