CVE-2026-64488 json
ALSA: aoa: check snd_ctl_new1() return value
published 2026-07-25 3 mo ago modified 2026-11-03 5 d ago also EUVD-2026-48832
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.39, 7.1.4, 7.2
- linux Debian 12 6.1.180-1
- linux Debian 13 6.12.100-1
- linux Debian 14 7.1.4-1
- linux-6.12 Debian 12 6.12.100-1~deb12u1
debian advisories DEBIAN-CVE-2026-64488
- linux Ubuntu 22.04 LTS 5.15.0-198.208
- linux Ubuntu 24.04 LTS 6.8.0-147.147
- linux Ubuntu 26.04 LTS 7.0.0-31.31
- linux-aws Ubuntu 22.04 LTS 5.15.0-1117.124
- linux-aws Ubuntu 24.04 LTS 6.8.0-1067.70
- linux-aws Ubuntu 26.04 LTS 7.0.0-1012.12
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1118.128
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1071.79
ubuntu advisories UBUNTU-CVE-2026-64488
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source openSUSE Tumbleweed 7.1.7-1.1
opensuse advisories openSUSE-SU-2026:11476-1
- git.kernel.org/stable/c/b0154ebc6dc552c389a574b1e221d728e10346e7 commit
- git.kernel.org/stable/c/d62624fe256b2d0d13454c78cbfc70ff5d954dc7 commit
- git.kernel.org/stable/c/e5e8c4508d95af82f9b4d065f658e5476a8e9bc8 commit
- git.kernel.org/stable/c/2ee9c46fd2dcd529cef18e37636ee12f5c3dbedd commit
- git.kernel.org/stable/c/d73067e2bbf3775a495d9f38e38d0a3cf53ee790 commit
- git.kernel.org/stable/c/fd786466889e4a6e6de0f4462bd0068edea63960 commit
- git.kernel.org/stable/c/e47f2a341adbac001b6f5d0211b0cd1c1668637b commit
- git.kernel.org/stable/c/8df560fefe6fed6a20b7e06720eeaeccec349ac0 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-64488 updated cvss 5.5
kernel: ALSA: aoa: check snd_ctl_new1() return value
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/b0154ebc6dc552c389a574b1e221d728e10346e7
- git.kernel.org /stable/c/d62624fe256b2d0d13454c78cbfc70ff5d954dc7
- git.kernel.org /stable/c/e5e8c4508d95af82f9b4d065f658e5476a8e9bc8
- git.kernel.org /stable/c/2ee9c46fd2dcd529cef18e37636ee12f5c3dbedd
- git.kernel.org /stable/c/d73067e2bbf3775a495d9f38e38d0a3cf53ee790
- git.kernel.org /stable/c/fd786466889e4a6e6de0f4462bd0068edea63960
- git.kernel.org /stable/c/e47f2a341adbac001b6f5d0211b0cd1c1668637b
- git.kernel.org /stable/c/8df560fefe6fed6a20b7e06720eeaeccec349ac0
Sources
- CVE List CVE-2026-64488
- NVD CVE-2026-64488
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.