CVE-2026-23208
Linux Kernel vulnerability analysis and mitigation

Overview

CVE-2026-23208 is an out-of-bounds write vulnerability in the Linux kernel's ALSA USB audio subsystem (sound/usb/pcm.c) caused by insufficient validation of the number of frames in a single data URB during PCM playback. A local attacker with low privileges can trigger a slab-out-of-bounds write by crafting USB audio parameters (e.g., maxpacksize 40, rate 22050/pps 1000) such that the calculated frame count exceeds the allocated URB buffer size. The vulnerability was published on February 14, 2026, and patches were released on March 18, 2026. Affected kernel versions span from 4.14.186 through 6.18.x (before 6.18.10), with specific point releases also affected; it carries a CVSS v3.1 base score of 7.8 (High) (Feedly, Kernel Patches).

Technical details

The root cause is classified as CWE-787 (Out-of-bounds Write). In prepare_playback_urb() (sound/usb/pcm.c:1611), the number of frames is calculated as packsize[0] * packets without verifying that this value does not exceed the URB buffer size, which is allocated as maxpacksize * packets. With crafted parameters (e.g., packsize[0]=22, packets=12, maxpacksize=40), the frame count (264) can exceed the buffer (240), triggering a KASAN-detected slab-out-of-bounds write in copy_to_urb() at offset sound/usb/pcm.c:1487. Exploitation requires local access and the ability to perform write operations on an ALSA PCM playback stream with attacker-controlled USB audio device parameters. The bug was originally identified by syzbot fuzzing (Feedly).

Impact

Successful exploitation can result in high confidentiality, integrity, and availability impact on the affected system, as the out-of-bounds write corrupts kernel heap memory. This could lead to kernel crashes (denial of service), privilege escalation, or arbitrary code execution in kernel context, potentially allowing an attacker to fully compromise the host. The scope is limited to the local system (no network-based exploitation), but kernel-level compromise enables lateral movement within a multi-tenant or containerized environment (Feedly).

Exploitation steps

  1. Gain local access: Obtain a low-privileged local account on a system running a vulnerable Linux kernel version (e.g., 5.8 through 6.18.9).
  2. Attach or emulate a USB audio device: Use a crafted or emulated USB audio device (e.g., via USB gadget or syzkaller-style device emulation) configured with maxpacksize=40 and a sample rate of 22050 Hz at 1000 packets per second.
  3. Open ALSA PCM playback stream: Open the corresponding ALSA PCM device (e.g., /dev/snd/pcmC0D0p) for playback with the crafted device parameters.
  4. Trigger the write: Perform a write operation to the PCM stream, causing prepare_playback_urb() to calculate a frame count (packsize[0] * packets = 264) that exceeds the URB buffer size (maxpacksize * packets = 240), triggering the out-of-bounds write in copy_to_urb() at sound/usb/pcm.c:1487.
  5. Achieve kernel memory corruption: The slab-out-of-bounds write corrupts adjacent kernel heap memory, which can be leveraged for privilege escalation or denial of service depending on heap layout (Feedly).

Indicators of compromise

  • Logs: Kernel logs (dmesg) showing BUG: KASAN: slab-out-of-bounds in copy_to_urb+0x261/0x460 sound/usb/pcm.c:1487 or Write of size 264 at addr ffff88804337e800; stack traces referencing prepare_playback_urb, prepare_outbound_urb, or copy_to_urb in the USB audio subsystem.
  • Process: Unusual processes (e.g., syz.0.* or custom tools) performing repeated open/write operations on ALSA PCM devices (/dev/snd/pcmC*D*p).
  • Kernel: Unexpected kernel panics or system instability correlated with USB audio device attachment or PCM playback activity; KASAN or KFENCE reports in kernel logs related to sound/usb/pcm.c or sound/usb/endpoint.c (Feedly).

Mitigation and workarounds

The Linux kernel maintainers released patches on March 18, 2026, adding a bounds check on the number of single data URB frames during frame count calculation. Patches are available for multiple stable branches via the kernel stable tree (commits: 282aba5, 480a149, 62932d9, ab0b5e9, c4dc012, d67dde0, e0ed5a3, ef5749e). Users should update to kernel versions 4.14.188+, 4.19.132+, 5.4.51+, 5.7.8+, or 6.18.10+ as applicable to their branch. As a workaround where patching is not immediately possible, restricting local user access to ALSA PCM devices (e.g., via udev rules or removing USB audio kernel modules) can reduce exposure (Kernel Patches, Feedly).

Additional resources


SourceThis report was generated using AI

Related Linux Kernel vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-64557NONEN/A
  • Linux Kernel logoLinux Kernel
  • kernel-rt-selftests-internal
NoNoJul 29, 2026
CVE-2026-64556NONEN/A
  • Linux Kernel logoLinux Kernel
  • kernel-64k-devel
NoNoJul 29, 2026
CVE-2026-64555NONEN/A
  • Linux Kernel logoLinux Kernel
  • linux-azure-fde-6.14
NoNoJul 27, 2026
CVE-2026-64554NONEN/A
  • Linux Kernel logoLinux Kernel
  • linux-gcp-6.14
NoYesJul 27, 2026
CVE-2026-64553NONEN/A
  • Linux Kernel logoLinux Kernel
  • kernel-rt-64k-debug-modules-internal
NoYesJul 27, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management