Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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 <[email protected]>

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 611a96f6acf2e74fe28cb90908a9c183862348ce – < b3a346d5c99dd73cf84711f2a43e42691990efd2
    • affected 611a96f6acf2e74fe28cb90908a9c183862348ce – < 7ba01e0d3539d9cf0aef3e82938f1648147744cc
    • affected 611a96f6acf2e74fe28cb90908a9c183862348ce – < 98dbfbb38e297c25c5b0af4a9018d71ac25e8554
    • affected 611a96f6acf2e74fe28cb90908a9c183862348ce – < 441aaad150c57edaf57ee482a79a3bf4c5b7e353
    • affected 3089703ab71484a8b9a7641051181d11d60f870c
    • affected 50f63f11a6ddaa0d34574df72b3fa6ee257c057d
    • affected 6.10.14 – < 6.11
    • affected 6.11.3 – < 6.12
  • Linux · Linux

    • affected 6.12
    • unaffected < 6.12
    • unaffected 6.12.103 – ≤ 6.12.*
    • unaffected 6.18.44 – ≤ 6.18.*
    • unaffected 7.1.8 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-74500 badge
[![CVE-2026-74500](https://cveledger.app/badge/CVE-2026-74500.svg)](https://cveledger.app/cve/CVE-2026-74500)

Record last updated .