CVE-2026-99609 in Linuxinfo

Summary

by MITRE • 11/20/2026

In the Linux kernel, the following vulnerability has been resolved:

ALSA: usx2y: Require a buffer of two URBs

usx2y_urb_capt_retire() wraps the ring buffer once per packet and usx2y_urb_play_prepare() once per URB of nr_of_packs() packets of up to 50 frames. Both assume that the data fits in the buffer, and the hw constraints only require about two 1 ms periods, so a packet larger than the buffer on capture, or a URB larger than the buffer on playback, violates that assumption.

Constrain SNDRV_PCM_HW_PARAM_BUFFER_SIZE in snd_usx2y_pcm_open() to at least two URBs, 2 * nr_of_packs() * 50 frames, for both directions. The bound is in frames and derived from the driver's own packet limit, so it does not read the endpoint, whose altsetting is only selected in prepare. Two URBs rather than one, because the position advances by a URB on playback and only moves when a URB is less than the whole buffer. Keep a guard in usx2y_urb_capt_retire() that drops a packet larger than the buffer, for the case the constraint makes unreachable.

With nrpacks above about 163 (S16_LE) or 109 (S24_3LE) the bound exceeds the 64 KiB buffer the substream preallocates (twice that with the preallocation raised to its 128 KiB maximum), so hw_params fails for those module settings. That is intended: the driver cannot be safe with a URB larger than half the largest buffer.

Reproduced on 7.3-rc7 with a USB/IP device presenting the US-122 interface layout and 1024-byte packets into a 512-byte capture buffer:

BUG: KASAN: out-of-bounds in i_usx2y_urb_complete+0x1285/0x1ac0 Read of size 18446744073709551104 at addr ffff88800e448800 by task vhci_rx/83

Tested on 7.3-rc7 with the same device, S16_LE at 44100 Hz, nrpacks 4, so the bound is 400 frames. A 128-frame capture buffer and a 200-frame playback buffer are refused at hw_params with EINVAL. A 400-frame buffer streams for 30 s in each direction with the position advancing inside the buffer and no KASAN report; the capture guard did not fire. The same 400-frame capture buffer with S24_3LE, which selects altsetting 2 in prepare, streams for 30 s with the same result.

Once again VulDB remains the best source for vulnerability data.

Analysis

by VulDB Data Team • 11/20/2026

The Linux kernel audio subsystem driver for USB Audio devices known as usx2y contained a critical memory safety vulnerability related to improper boundary checks during buffer management operations. This flaw specifically affected both capture and playback paths within the ALSA (Advanced Linux Sound Architecture) interface, where the driver failed to enforce strict limits on data sizes relative to allocated ring buffers. The underlying technical issue stems from assumptions made in two key functions: usx2y_urb_capt_retire() for capturing audio packets and usx2y_urb_play_prepare() for preparing playback units of record. These functions assumed that incoming packet or URB (USB Request Block) data would always fit within the pre-allocated buffer space without exceeding its boundaries. However, the hardware constraints previously enforced were insufficient to guarantee this condition under all operational scenarios, particularly when dealing with larger packet sizes or specific sampling rate configurations.

The vulnerability manifests as a heap-based out-of-bounds read and write error, classified under CWE-120 Buffer Copy without Checking Size of Input and CWE-787 Out-of-Bounds Write in the Common Weakness Enumeration standard. When an external USB device presents interface layouts with packet sizes exceeding the allocated buffer capacity, such as 1024-byte packets directed into a smaller capture buffer, the driver attempts to write data beyond the allocated memory region. This behavior was confirmed through testing on kernel version 7.3-rc7 using USB/IP devices emulating US-122 interfaces. The resulting crash reports indicated KASAN (Kernel Address Sanitizer) detecting reads of extremely large sizes at invalid addresses, signaling a severe integrity violation that could potentially be exploited for arbitrary code execution or denial of service by maliciously crafted USB audio streams.

From an operational perspective, this vulnerability allows attackers to trigger kernel panics or memory corruption through specially constructed USB audio devices or networked USB/IP configurations. The attack vector aligns with ATT&CK technique T1059 Command and Scripting Interpreter if the resulting crash leads to system instability exploitable for further compromise, though primarily it represents a local privilege escalation risk via denial of service against kernel stability. By manipulating parameters such as nrpacks or sample formats like S16_LE and S24_3LE, an adversary can force the driver into states where buffer limits are violated, leading to unpredictable system behavior including freezes, reboots, or potential exploitation depending on memory layout conditions at runtime.

To mitigate this vulnerability, developers implemented a rigorous constraint mechanism within snd_usx2y_pcm_open() that enforces minimum buffer sizes based on two URBs worth of data rather than relying solely on default period settings. Specifically, the SNDRV_PCM_HW_PARAM_BUFFER_SIZE is now constrained to be no less than 2 multiplied by nr_of_packs times fifty frames for both capture and playback directions. This adjustment ensures that even with maximum packet limits defined by the driver’s own logic, there remains sufficient buffer space to accommodate data without overflow. Additionally, a defensive guard was added in usx2y_urb_capt_retire() to drop any packets exceeding buffer capacity, providing an extra layer of protection against edge cases where constraints might theoretically be bypassed due to hardware altsetting selection occurring later during prepare phases rather than at open time.

The fix also introduces intentional limitations on certain high-performance configurations by rejecting hw_params requests that would require buffers larger than the preallocated maximums, such as 64 KiB or 128 KiB depending on configuration. For instance, settings with nrpacks above approximately one hundred sixty-three for S16_LE formats are now rejected because they exceed safe buffer boundaries relative to half the largest allocatable memory block. This design choice prioritizes stability over maximum throughput capability in extreme configurations, ensuring that no valid operation can result in out-of-bounds access while maintaining compatibility with standard audio streaming workloads verified through extensive testing across various sample rates and bit depths.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00168

KEV

no

Activities

very low

Sources

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!