CVE-2026-80828 — ALSA: usb-audio: Complete cleanup after system-resume errors
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 88a8516a2128a6d078a106ead48092240e8a138f and < 3fa521c3c54b42e16cad8ade76551113a783752b≥ 88a8516a2128a6d078a106ead48092240e8a138f and < 3f06f3f5b16212f180764654a9398ff5f7a855c8≥ 88a8516a2128a6d078a106ead48092240e8a138f and < f1c05c41d07b874635d681ae328d13ec550470c5≥ 88a8516a2128a6d078a106ead48092240e8a138f and < 5a625fc2284e35f33693efd9534aebaca3b005d4≥ 88a8516a2128a6d078a106ead48092240e8a138f and < 6d3e202670b819c414076a5d07dffac8a39274ad≥ 88a8516a2128a6d078a106ead48092240e8a138f and < 6c94877b6bab9185898bcad4b082ff5592558921≥ 88a8516a2128a6d078a106ead48092240e8a138f and < d1f643b1c0258bd519146f7a342bbb394d413912≥ 88a8516a2128a6d078a106ead48092240e8a138f and < 1739a976312e110c93a8dee66a1cdf893a1b187e and 1 moreversion 2.6.39 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 26, 2026 · 11 reading(s) · max 0.19%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
10 on the record
- git.kernel.org/stable/c/1739a976312e110c93a8dee66a1cdf893a1b187e
- git.kernel.org/stable/c/3fa521c3c54b42e16cad8ade76551113a783752b
- git.kernel.org/stable/c/d1f643b1c0258bd519146f7a342bbb394d413912
- git.kernel.org/stable/c/5a625fc2284e35f33693efd9534aebaca3b005d4
- git.kernel.org/stable/c/6c94877b6bab9185898bcad4b082ff5592558921
- nvd.nist.gov/vuln/detail/CVE-2026-80828
- git.kernel.org/stable/c/3f06f3f5b16212f180764654a9398ff5f7a855c8
- github.com/advisories/GHSA-ccmv-3r92-jgv5
- git.kernel.org/stable/c/6d3e202670b819c414076a5d07dffac8a39274ad
- git.kernel.org/stable/c/f1c05c41d07b874635d681ae328d13ec550470c5
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99092 riscv: patch: fix handling of bpf-jit execmem addresses 23h
- Unknown CVE-2026-99093 mm: don't schedule deferred kernel page table freeing while booting 23h
- Unknown CVE-2026-99095 drm/vc4: drain the hangcheck timer and works on V3D unbind 23h
- Unknown CVE-2026-99096 io_uring/register: don't exempt disabled rings from task restrictions 23h
- Unknown CVE-2026-99097 tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper() 23h
- Unknown CVE-2026-99098 dm-integrity: fix buffer overflow in inline mode with large tag size 23h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-80828 is "ALSA: usb-audio: Complete cleanup after system-resume errors", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.19% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.