CVE-2026-74500
CVE CVE-2026-74500EUVD EUVD-2026-59693Published 2026-08-15T12:27:26.000ZLast changed 2026-08-17T05:20:38.000Z
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: fix stack info leak in RME Digiface status snd_rme_digiface_read_status() reads a four-word status block from the device into an uninitialised on-stack __le32 buf[4] and, whenever the vendor control-IN transfer does not return a negative error, copies all four words into the caller's status[]. snd_usb_ctl_msg() copies the full requested size back into the caller's buffer regardless of how many bytes the data stage actually delivered: buf = kmemdup(data, size, GFP_KERNEL); err = usb_control_msg(dev, pipe, request, requesttype, value, index, buf, size, timeout); memcpy(data, buf, size); usb_control_msg() returns the transferred length on a short control-IN, which is a non-negative value, and writes only that many bytes. The remainder of the copy back is the kmemdup()ed image of the caller's buffer, so a device answering with a short data stage leaves the trailing words of buf[] holding leftover kernel stack. The only guard in the caller is err < 0, so those words are stored into status[]. They then reach user space: snd_rme_digiface_get_status_val() selects a 16-bit halfword of status[] per the control's reg/mask, and the eight Digiface status controls together expose the whole 16-byte frame to an unprivileged reader of /dev/snd/controlC*. Zero-initialise the buffer so a short read yields zeros instead of stack residue. This mirrors snd_rme_get_status1(), which already clears its output word before the same kind of vendor read. Discovered by XBOW, triaged by Baul Lee <baul.lee@xbow.com>
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 50f63f11a6ddaa0d34574df72b3fa6ee257c057d; patch: 6.12.103; 6.11.3 <6.12; 611a96f6acf2e74fe28cb90908a9c183862348ce <441aaad150c57edaf57ee482a79a3bf4c5b7e353; patch: 7.1.8; 6.10.14 <6.11; 611a96f6acf2e74fe28cb90908a9c183862348ce <b3a346d5c99dd73cf84711f2a43e42691990efd2; patch: 0; patch: 6.18.44; 611a96f6acf2e74fe28cb90908a9c183862348ce <7ba01e0d3539d9cf0aef3e82938f1648147744cc; 611a96f6acf2e74fe28cb90908a9c183862348ce <98dbfbb38e297c25c5b0af4a9018d71ac25e8554; 6.12; patch: 7.2; 3089703ab71484a8b9a7641051181d11d60f870c
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.