What’s Vulnerable › Vulnerabilities
CVE-2026-72446: ALSA: usb-audio: qcom: reject stream disable with no active interface
- Severity: high (CVSS 7.8 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.2% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-08-15 · updated 2026-08-17
Description
In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: qcom: reject stream disable with no active interface handle_uaudio_stream_req() resolves an interface index with info_idx_from_ifnum(), which returns -EINVAL when no interface matches. The enable branch and the response: cleanup label both guard against a negative index, but the disable branch does not: it forms info = &uadev[pcm_card_num].info[info_idx] and dereferences it. uadev[].info is a pointer allocated only when a stream is first enabled, so a negative info_idx on the disable path is unsafe in two ways: - If the card was never enabled, .info is NULL and &info[-EINVAL] is a wild pointer; reading info->data_ep_pipe faults (kernel oops). - If the card was enabled at least once (.info allocated) and the disable names an interface that does not match, &info[-EINVAL] points before the allocation; info->data_ep_pipe / info->sync_ep_pipe are an out-of-bounds slab read and, when non-zero, an out-of-bounds 4-byte write (both pipe fields are cleared to 0). That is memory corruption, not just a NULL dereference. The request is reachable from unprivileged local userspace over AF_QIPCRTR. Reject a disable request with no resolved interface, matching the guard the enable path already has.
Affected products
- Linux kernel: 6.16 — fixed in 7.2
How to fix
Upgrade to a fixed version: Linux kernel 7.2. Check the vendor advisory for mitigations.
References
- https://git.kernel.org/stable/c/25a867aa5e67a84333fa6e5c21292c5bcff86b90
- https://git.kernel.org/stable/c/a22356d1f731553e99aa2707dbd38c659bdd28d8
- https://git.kernel.org/stable/c/bdb640be82e645e2828731648f485224d0c2587b
Get alerted when CVE-2026-72446 or the next vulnerability affects your stack