CVE-2026-43437: ALSA: pcm: fix use-after-free on linked stream runtime in snd_pcm_drain()

Published May 8, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

ALSA: pcm: fix use-after-free on linked stream runtime in sndpcmdrain()

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->noperiodwakeup, runtime->rate, and runtime->buffersize (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 sndpcmreleasesubstream() → sndpcmdrop() → pcmreleaseprivate() → sndpcmunlink() → sndpcmdetachsubstream() → kfree(runtime). No synchronization prevents kfree(runtime) from completing while the drain path dereferences the stale pointer.

Fix by caching the needed runtime fields (noperiodwakeup, rate, buffersize) into local variables while still holding the stream lock, and using the cached values after the lock is released.

Affected Software

10 affected components
Linux Linux kernel (ALSA pcm)
Linux Linux kernel>=3.0<5.10.253
Linux Linux kernel>=5.11<6.1.167
Linux Linux kernel>=6.2<6.6.130
Linux Linux kernel>=6.7<6.12.78
Linux Linux kernel>=6.13<6.18.19
Linux Linux kernel>=6.19<6.19.9
Linux Linux kernel=7.0-rc1
Linux Linux kernel=7.0-rc2
Linux Linux kernel=7.0-rc3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Mitigate by avoiding concurrent close() of the linked ALSA PCM stream file descriptor while snd_pcm_drain() is running, since the fix addresses a use-after-free triggered by concurrent close() on the linked stream's fd.

Event History

May 8, 2026
CVE Published
via MITRE·02:22 PM
Data Sourced
via MITRE·02:22 PM
DescriptionSeverity
Data Sourced
via NVD·03:16 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-43437?

The severity of CVE-2026-43437 is high with a CVSS score of 7.8.

2

How do I fix CVE-2026-43437?

You can fix CVE-2026-43437 by applying the available patches provided in the Linux kernel updates.

3

What type of vulnerability is CVE-2026-43437?

CVE-2026-43437 is classified as a Use After Free vulnerability.

4

What impact does CVE-2026-43437 have on systems?

CVE-2026-43437 can lead to potential information disclosure and system instability due to the use-after-free condition in ALSA.

5

Which software is affected by CVE-2026-43437?

CVE-2026-43437 affects the Linux kernel, specifically the ALSA PCM subsystem.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203