REDHAT-BUG-2439947: Medium severity Linux ALSA aloop driver vulnerability
In the Linux kernel, the following vulnerability has been resolved:
ALSA: aloop: Fix racy access at PCM trigger
The PCM trigger callback of aloop driver tries to check the PCM state and stop the stream of the tied substream in the corresponding cable. Since both check and stop operations are performed outside the cable lock, this may result in UAF when a program attempts to trigger frequently while opening/closing the tied stream, as spotted by fuzzers.
For addressing the UAF, this patch changes two things: - It covers the most of code in loopbackcheckformat() with cable->lock spinlock, and add the proper NULL checks. This avoids already some racy accesses. - In addition, now we try to check the state of the capture PCM stream that may be stopped in this function, which was the major pain point leading to UAF.
Affected Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-2439947?
The severity of REDHAT-BUG-2439947 is medium with a risk score of 4.
How do I fix REDHAT-BUG-2439947?
To fix REDHAT-BUG-2439947, update the Linux ALSA aloop driver to the latest patched version.
What issue does REDHAT-BUG-2439947 address?
REDHAT-BUG-2439947 addresses a race condition in the PCM trigger callback of the aloop driver.
Which component is affected by REDHAT-BUG-2439947?
The Linux ALSA aloop driver is the component affected by REDHAT-BUG-2439947.
When was REDHAT-BUG-2439947 published?
REDHAT-BUG-2439947 was published on February 14, 2026.