CVE-2026-53242

ALSA: PCM: Fix wait queue list corruption in snd_pcm_drain() on linked streams

HIGH
7.8
CVSS Score
Published: June 25, 2026 at 08:39 AM UTC
Updated: October 19, 2026 at 08:19 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: ALSA: PCM: Fix wait queue list corruption in snd_pcm_drain() on linked streams snd_pcm_drain() uses init_waitqueue_entry which does not clear entry.prev/next, and add_wait_queue with a conditional remove_wait_queue that is skipped when to_check is no longer in the group after concurrent UNLINK. The orphaned wait entry remains on the unlinked substream sleep queue. On the next drain iteration, add_wait_queue adds the entry to a new queue while still linked on the old one, corrupting both lists. A subsequent wake_up dereferences NULL at the func pointer (mapped from the spinlock at offset 0 of the misinterpreted wait_queue_head_t), causing a kernel panic. Replace init_waitqueue_entry/add_wait_queue/conditional remove_wait_queue with init_wait_entry/prepare_to_wait/ finish_wait. init_wait_entry clears prev/next via INIT_LIST_HEAD on each iteration and sets autoremove_wake_function which auto-removes the entry on wake-up. finish_wait safely handles both the already-removed and still-queued cases.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.10.253 ≤ v < 5.10.2596.1.167 ≤ v < 6.1.1766.12.78 ≤ v < 6.12.946.18.19 ≤ v < 6.18.366.19.9 ≤ v < 7.06.6.130 ≤ v < 6.6.1437.0.1 ≤ v < 7.0.134a758e9a1f5ed722f83c4dd35f867fe811553bcb5.10.2536.1.1676.12.786.18.196.19.96.6.130629cf09464cf98670996ea5c191dc9743e6f3f007.07.0 rc47.0 rc57.0 rc67.0 rc77.17.1 rc17.1 rc27.1 rc37.1 rc47.1 rc57.1 rc69b1dbd69ba6f8f8c69bc7b77c2ce3b9c6ed05ba69baee36e8c5443411c4629afabafaff8a46a23fdae8f8d30d334bad5b1b3cdb1eb8a0b771f55e432c2f64e05a0587a83ec42dbd6b7a7ded79b2ff694f2cb2e0d27fb925c73a78f0ce7d6dbf68d3747c1fc71f888994569f87d5bee20b1ac6c9c1e3a7a79
Vendor states this is fixed in 06eca2235a3fd281dddf25b0a97772b25b5bb573 (fixed)
Vendor states this is fixed in 7c71a9522555ff137a9ca36b15d759ca04d84788 (fixed)
Vendor states this is fixed in 88fe2e3658726cb21ff2dcf9770bf672f9b9d31b (fixed)
Vendor states this is fixed in b053fcd8912f06c30f932f5b8ec41c72de474695 (fixed)
Vendor states this is fixed in cac5bf3500ee6422cf64e0df0b5daeecfed42917 (fixed)
Vendor states this is fixed in cd98837db15f323463b8df07282ac723bd5c3fed (fixed)
Vendor states this is fixed in d68b621bb5a48051932f1017a6e1bc9b18f854d0 (fixed)
Vendor states this is fixed in d842f26a167e77a36f3ed333b9fa99d36ef99fe6 (fixed)
Vendor states this is fixed in 5.10.259 (unaffected)
Vendor states this is fixed in 6.1.176 (unaffected)
Vendor states this is fixed in 6.12.94 (unaffected)
Vendor states this is fixed in 6.18.36 (unaffected)
Affected range stops below 6.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.6.143 (unaffected)
Vendor states this is fixed in 7.0 (unaffected)
Vendor states this is fixed in 7.0.13 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-476CWE-362

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card