# CVE-2026-64001: ALSA: pcm: oss: Fix setup list UAF on proc write error

> A use-after-free in the Linux kernel ALSA OSS driver allows local attackers to execute code or escalate privileges via a race condition during proc write errors.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 19 Jul 2026
- **Updated:** 21 Oct 2026
- **Also known as:** BELL-CVE-2026-64001, DEBIAN-CVE-2026-64001, GHSA-w765-6pj3-4x6v, ROOT-OS-DEBIAN-11-CVE-2026-64001, ROOT-OS-DEBIAN-12-CVE-2026-64001, ROOT-OS-UBUNTU-2204-CVE-2026-64001, UBUNTU-CVE-2026-64001

## What is CVE-2026-64001?

CVE-2026-64001 is a high-severity use after free vulnerability in Linux kernel, published on 19 Jul 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: pcm: oss: Fix setup list UAF on proc write error

snd_pcm_oss_proc_write() links a newly allocated setup entry into the
OSS setup list before duplicating the task name. If the task-name
allocation fails, the error path frees the already linked entry and
leaves setup_list pointing at freed memory.

A later OSS device open can then walk the stale list entry in
snd_pcm_oss_look_for_setup() and dereference freed memory.

Allocate the task name and initialize the setup entry before publishing
the entry on setup_list. Also fetch the initial proc read iterator only
after taking setup_mutex, so all setup_list traversal follows the same
list lifetime rules.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2026-64001 being exploited?

There is no known exploitation of CVE-2026-64001 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-64001 and fix it if it is affected.

What it is: CVE-2026-64001 is a high-severity use after free vulnerability in Linux kernel, published on 19 Jul 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-64001 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-64001/ (Markdown: https://insights.sbomify.com/CVE-2026-64001/index.md)
```

## Sources

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

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