CVE-2026-80716: ALSA: pcm: wake linked drain waiters on unlink
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1c1b7e8e545ce65e40f65b55c432765e058ea98f, 2940cc3cf43c72126b74ee6376314c195382023a, 3035bb784cea3f338934f5042dd3f35225a51b2e.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1c1b7e8e545ce65e40f65b55c432765e058ea98f, 2940cc3cf43c72126b74ee6376314c195382023a, 3035bb784cea3f338934f5042dd3f35225a51b2e or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: wake linked drain waiters on unlink snd_pcm_drain() on a linked stream parks an on-stack wait entry on the drained peer's runtime->sleep, and after schedule_timeout() removes it only if that peer is still found in the caller's group. If group membership changes during the wait and the sleep ends by signal or timeout (so autoremove_wake_function() does not run), finish_wait() is skipped and snd_pcm_drain() returns with the entry still queued on that stream's sleep list; a later wake_up() then walks a freed stack frame. This is reachable by unlinking either the drained or the draining stream. Unlike the close path (snd_pcm_drop() -> snd_pcm_post_stop()), snd_pcm_unlink() never wakes the sleep queues. Wake every group member under the group lock before the membership change, so a linked drainer is released and drops its entry while the streams are still grouped. The window was opened when snd_pcm_link_rwsem stopped being held across the wait and the removal became conditional on group membership (see Fixes). The later switch to finish_wait() kept that conditional removal, so the signal/timeout case remained.
- Published
- Aug 28, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.1affected
- f57f3df03a8e6010e321fa0258d3e054713c3cb7 and later · before c172e4c53321ee6429955295ea133bc3597a3ca9affected · git
- f57f3df03a8e6010e321fa0258d3e054713c3cb7 and later · before 3035bb784cea3f338934f5042dd3f35225a51b2eaffected · git
- f57f3df03a8e6010e321fa0258d3e054713c3cb7 and later · before 1c1b7e8e545ce65e40f65b55c432765e058ea98faffected · git
- f57f3df03a8e6010e321fa0258d3e054713c3cb7 and later · before e8b784a3f4fba3ea9c4d05138ecfa784a069627faffected · git
- f57f3df03a8e6010e321fa0258d3e054713c3cb7 and later · before e8315330e4ec09c0cac625515400e13d0ee22b81affected · git
- f57f3df03a8e6010e321fa0258d3e054713c3cb7 and later · before 2940cc3cf43c72126b74ee6376314c195382023aaffected · git
- f57f3df03a8e6010e321fa0258d3e054713c3cb7 and later · before db09bc4ab19ce548a078240d2374792523953500affected · git
- f57f3df03a8e6010e321fa0258d3e054713c3cb7 and later · before f495b6c4c8594122918552c9be2b51eb71647cd9affected · git
- before 5.1not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.8-1 | 7.1.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80714Aug 28, 2026 · ipvs: do not propagate one-packet flag to synced conns39Monitor
- ← EarlierCVE-2026-80715Aug 28, 2026 · igc: remove napi_synchronize() in igc_down()0Monitor
- Later →CVE-2026-80717Aug 28, 2026 · sctp: validate Adaptation Indication parameter length30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1c1b7e8e545ce65e40f65b55c432765e058ea98f | Vendor (CNA) |
| Linux Linux | 2940cc3cf43c72126b74ee6376314c195382023a | Vendor (CNA) |
| Linux Linux | 3035bb784cea3f338934f5042dd3f35225a51b2e | Vendor (CNA) |
| Linux Linux | c172e4c53321ee6429955295ea133bc3597a3ca9 | Vendor (CNA) |
| Linux Linux | db09bc4ab19ce548a078240d2374792523953500 | Vendor (CNA) |
| Linux Linux | e8315330e4ec09c0cac625515400e13d0ee22b81 | Vendor (CNA) |
| Linux Linux | e8b784a3f4fba3ea9c4d05138ecfa784a069627f | Vendor (CNA) |
| Linux Linux | f495b6c4c8594122918552c9be2b51eb71647cd9 | Vendor (CNA) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0945 · Aug 31, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2940cc3cf43c72126b74ee6376314c195382023a
- git.kernel.org/stable/c/3035bb784cea3f338934f5042dd3f35225a51b2e
- git.kernel.org/stable/c/c172e4c53321ee6429955295ea133bc3597a3ca9
- git.kernel.org/stable/c/db09bc4ab19ce548a078240d2374792523953500
- git.kernel.org/stable/c/e8315330e4ec09c0cac625515400e13d0ee22b81
- git.kernel.org/stable/c/e8b784a3f4fba3ea9c4d05138ecfa784a069627f
- git.kernel.org/stable/c/f495b6c4c8594122918552c9be2b51eb71647cd9
Vendor advisories and official records. Exploit/PoC links are deliberately left out.