# CVE-2026-23076: ALSA: ctxfi: Fix potential OOB access in audio mixer handling

> Out-of-bounds access in the ALSA ctxfi audio mixer driver allows attackers to cause denial of service or potentially execute code.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Feb 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-77256, BELL-CVE-2026-23076, DEBIAN-CVE-2026-23076, GHSA-9325-8xwg-7r9m, ROOT-OS-DEBIAN-11-CVE-2026-23076, ROOT-OS-DEBIAN-12-CVE-2026-23076, ROOT-OS-DEBIAN-13-CVE-2026-23076, ROOT-OS-UBUNTU-2204-CVE-2026-23076, ROOT-OS-UBUNTU-2404-CVE-2026-23076, UBUNTU-CVE-2026-23076

## What is CVE-2026-23076?

CVE-2026-23076 is a high-severity memory corruption vulnerability in Linux kernel, published on 4 Feb 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: ctxfi: Fix potential OOB access in audio mixer handling

In the audio mixer handling code of ctxfi driver, the conf field is
used as a kind of loop index, and it's referred in the index callbacks
(amixer_index() and sum_index()).

As spotted recently by fuzzers, the current code causes OOB access at
those functions.
| UBSAN: array-index-out-of-bounds in /build/reproducible-path/linux-6.17.8/sound/pci/ctxfi/ctamixer.c:347:48
| index 8 is out of range for type 'unsigned char [8]'

After the analysis, the cause was found to be the lack of the proper
(re-)initialization of conj field.

This patch addresses those OOB accesses by adding the proper
initializations of the loop indices.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2026-23076 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-23076 is a high-severity memory corruption vulnerability in Linux kernel, published on 4 Feb 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-23076 in the wild and no public exploit code.

Affected product: Linux kernel. 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-23076/ (Markdown: https://insights.sbomify.com/CVE-2026-23076/index.md)
```

## Sources

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

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