Bug 2492710 (CVE-2026-53242) - CVE-2026-53242 kernel: ALSA: PCM: Fix wait queue list corruption in snd_pcm_drain() on linked streams
Summary: CVE-2026-53242 kernel: ALSA: PCM: Fix wait queue list corruption in snd_pcm_d...
Keywords:
Status: NEW
Alias: CVE-2026-53242
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-25 10:01 UTC by OSIDB Bzimport
Modified: 2026-06-26 10:37 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-06-25 10:01:43 UTC
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.

Comment 1 Mauro Matteo Cascella 2026-06-26 10:29:52 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026062511-CVE-2026-53242-45ab@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.