cveboard RSS feed

CVE-2026-74500

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2026
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

ALSA: usb-audio: fix stack info leak in RME Digiface status

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>

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
unaffected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
611a96f6acf2e74fe28cb90908a9c183862348ceaffectedgitb3a346d5c99dd73cf84711f2a43e42691990efd2UnavailableNone listed
611a96f6acf2e74fe28cb90908a9c183862348ceaffectedgit7ba01e0d3539d9cf0aef3e82938f1648147744ccUnavailableNone listed
611a96f6acf2e74fe28cb90908a9c183862348ceaffectedgit98dbfbb38e297c25c5b0af4a9018d71ac25e8554UnavailableNone listed
611a96f6acf2e74fe28cb90908a9c183862348ceaffectedgit441aaad150c57edaf57ee482a79a3bf4c5b7e353UnavailableNone listed
3089703ab71484a8b9a7641051181d11d60f870caffectedgitUnavailableUnavailableNone listed
50f63f11a6ddaa0d34574df72b3fa6ee257c057daffectedgitUnavailableUnavailableNone listed
6.10.14affectedsemver6.11UnavailableNone listed
6.11.3affectedsemver6.12UnavailableNone listed

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
affected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
6.12affectedUnavailableUnavailableUnavailableNone listed
0unaffectedsemver6.12UnavailableNone listed
6.12.103unaffectedsemverUnavailable6.12.*None listed
6.18.44unaffectedsemverUnavailable6.18.*None listed
7.1.8unaffectedsemverUnavailable7.1.*None listed
7.2unaffectedoriginal_commit_for_fixUnavailable*None listed