# CVE-2026-64488: ALSA: aoa: check snd_ctl_new1() return value

> A missing NULL check in the Linux kernel ALSA aoa driver allows a local attacker to cause a denial of service via memory allocation failure.

- **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:** 25 Jul 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-64488, DEBIAN-CVE-2026-64488, GHSA-f8vw-v29r-vg8c, ROOT-OS-UBUNTU-2204-CVE-2026-64488, UBUNTU-CVE-2026-64488

## What is CVE-2026-64488?

CVE-2026-64488 is a vulnerability in Linux, published on 25 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: aoa: check snd_ctl_new1() return value

snd_ctl_new1() can return NULL when memory allocation fails. In
layout.c, the function does not check the return value before
dereferencing ctl->id.name or passing to aoa_snd_ctl_add(), which can
lead to a NULL pointer dereference.

Add NULL checks after snd_ctl_new1() calls and return early if any
fails.

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


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

Apply the vendor's patch.

## Is CVE-2026-64488 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-64488 is a vulnerability in Linux, published on 25 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-64488 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-64488/ (Markdown: https://insights.sbomify.com/CVE-2026-64488/index.md)
```

## Sources

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

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