CVE-2026-74498

ALSA: usb-audio: Fix DMA buffer out-of-bounds write when fill_max is set

N/A
Published: August 15, 2026 at 12:27 PM UTC
Updated: August 19, 2026 at 05:21 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Fix DMA buffer out-of-bounds write when fill_max is set When a USB audio endpoint requests full packet transfers via the fill_max descriptor flag, data_ep_set_params() promotes ep->curpacksize to ep->maxpacksize. However, maxsize is left at the original sample-rate derived value. Since u->buffer_size is allocated as maxsize * packets, the resulting DMA buffer is far too small for the requested transfer length. When the USB host controller streams up to curpacksize bytes per packet, it writes past the end of the buffer via DMA, corrupting kernel heap memory. Update maxsize to curpacksize when fill_max is set so that the allocated DMA buffer size matches the actual transfer request size. [ changed to reassign maxsize only when ep->fill_max is set -- tiwai ]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.5 ≤ v < 5.10.2653.5 ≤ v < 5.15.2163.5 ≤ v < 6.1.1833.5 ≤ v < 6.12.1033.5 ≤ v < 6.18.443.5 ≤ v < 6.6.1513.5 ≤ v < 7.1.83.5 ≤ v < 7.23.58fdff6a319e7dac757c558bd283dc4577e68cde7
Vendor states this is fixed in 04595233e5606d452f9f47e6989fc7ae7440fd40 (fixed)
Vendor states this is fixed in 10c24e6fddf4bdff0b6b05a47a4347b38e6960e8 (fixed)
Vendor states this is fixed in 3852974608f53e530e27c21d0c6c7d79c17b3f5a (fixed)
Vendor states this is fixed in 6cbdd11f9b05b92f4aa29f09a66e19ed0e25e66c (fixed)
Vendor states this is fixed in b1770f9ac35c0ffc34914d52347c65dcd5ac049b (fixed)
Vendor states this is fixed in bd65b7191683bebd9923904f0558b9211b9129da (fixed)
Vendor states this is fixed in d0199ae1666ff9ae2d1d568d64c3430d4c47f0e5 (fixed)
Vendor states this is fixed in f9b6c9576568169139ac151f7881474f384659fd (fixed)
Vendor states this is fixed in 3.5 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card