Answer in brief
CVE-2026-43437 records a Unknown severity vulnerability in ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-43437 records a Unknown severity vulnerability in ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f2b3614cefb61ee6046a0aaee503ee37f227d310 <9baee36e8c5443411c4629afabafaff8a46a23fd || >=f2b3614cefb61ee6046a0aaee503ee37f227d310 <fc71f888994569f87d5bee20b1ac6c9c1e3a7a79 || >=f2b3614cefb61ee6046a0aaee503ee37f227d310 <629cf09464cf98670996ea5c191dc9743e6f3f00 || >=f2b3614cefb61ee6046a0aaee503ee37f227d310 <ae8f8d30d334bad5b1b3cdb1eb8a0b771f55e432 || >=f2b3614cefb61ee6046a0aaee503ee37f227d310 <4a758e9a1f5ed722f83c4dd35f867fe811553bcb || >=f2b3614cefb61ee6046a0aaee503ee37f227d310 <c2f64e05a0587a83ec42dbd6b7a7ded79b2ff694 || >=f2b3614cefb61ee6046a0aaee503ee37f227d310 <9b1dbd69ba6f8f8c69bc7b77c2ce3b9c6ed05ba6 | 9baee36e8c5443411c4629afabafaff8a46a23fd, fc71f888994569f87d5bee20b1ac6c9c1e3a7a79, 629cf09464cf98670996ea5c191dc9743e6f3f00, ae8f8d30d334bad5b1b3cdb1eb8a0b771f55e432, 4a758e9a1f5ed722f83c4dd35f867fe811553bcb, c2f64e05a0587a83ec42dbd6b7a7ded79b2ff694, 9b1dbd69ba6f8f8c69bc7b77c2ce3b9c6ed05ba6 |
| Linux/Linuxgeneric | 3.0 | Not reported |
Published upstream
May 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f2b3614cefb61ee6046a0aaee503ee37f227d310 <9baee36e8c5443411c4629afabafaff8a46a23fd || >=f2b3614cefb61ee6046a0aaee503ee37f227d310 <fc71f888994569f87d5bee20b1ac6c9c1e3a7a79 || >=f2b3614cefb61ee6046a0aaee503ee37f227d310 <629cf09464cf98670996ea5c191dc9743e6f3f00 || >=f2b3614cefb61ee6046a0aaee503ee37f227d310 <ae8f8d30d334bad5b1b3cdb1eb8a0b771f55e432 || >=f2b3614cefb61ee6046a0aaee503ee37f227d310 <4a758e9a1f5ed722f83c4dd35f867fe811553bcb || >=f2b3614cefb61ee6046a0aaee503ee37f227d310 <c2f64e05a0587a83ec42dbd6b7a7ded79b2ff694 || >=f2b3614cefb61ee6046a0aaee503ee37f227d310 <9b1dbd69ba6f8f8c69bc7b77c2ce3b9c6ed05ba6 | 9baee36e8c5443411c4629afabafaff8a46a23fd, fc71f888994569f87d5bee20b1ac6c9c1e3a7a79, 629cf09464cf98670996ea5c191dc9743e6f3f00, ae8f8d30d334bad5b1b3cdb1eb8a0b771f55e432, 4a758e9a1f5ed722f83c4dd35f867fe811553bcb, c2f64e05a0587a83ec42dbd6b7a7ded79b2ff694, 9b1dbd69ba6f8f8c69bc7b77c2ce3b9c6ed05ba6 |
| Linux/Linuxgeneric | 3.0 | Not reported |
Published upstream
May 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.