ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f2b3614cefb61ee6046a0aaee503ee37f227d310 · < 4a758e9a1f5ed722f83c4dd35f867fe811553bcb| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain()
In the drain loop, the local variable 'runtime' is reassigned to a linked stream's runtime (runtime = s->runtime at line 2157). After releasing the stream lock at line 2169, the code accesses runtime->no_period_wakeup, runtime->rate, and runtime->buffer_size (lines 2170-2178) — all referencing the linked stream's runtime without any lock or refcount protecting its lifetime.
A concurrent close() on the linked stream's fd triggers snd_pcm_release_substream() → snd_pcm_drop() → pcm_release_private() → snd_pcm_unlink() → snd_pcm_detach_substream() → kfree(runtime). No synchronization prevents kfree(runtime) from completing while the drain path dereferences the stale pointer.
Fix by caching the needed runtime fields (no_period_wakeup, rate, buffer_size) into local variables while still holding the stream lock, and using the cached values after the lock is released.
From the CVE record · Linux
The Linux kernel's ALSA PCM drain path can access a linked stream's runtime after its lock is released. A concurrent close of the linked stream can free that runtime, causing a use-after-free during drain. This requires concurrent local operations on linked streams; the input does not specify authentication requirements.
Engineers running Linux kernels with ALSA PCM support should check their kernel versions; affected versions are not specified.