VYPR
Medium severity5.5NVD Advisory· Published May 6, 2026· Updated May 11, 2026

CVE-2026-43204

CVE-2026-43204

Description

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

ASoC: qcom: q6asm: drop DSP responses for closed data streams

'Commit a354f030dbce ("ASoC: qcom: q6asm: handle the responses after closing")' attempted to ignore DSP responses arriving after a stream had been closed.

However, those responses were still handled, causing lockups.

Fix this by unconditionally dropping all DSP responses associated with closed data streams.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Linux kernel's ASoC q6asm driver mishandles DSP responses for closed streams, causing lockups; fix drops such responses unconditionally.

The vulnerability in the Linux kernel's ASoC q6asm driver occurs because DSP responses are still processed after a data stream has been closed. A previous commit attempted to ignore these responses but the handling was incomplete, leading to kernel lockups [1][2]. The root cause is that the driver did not properly discard responses for closed streams, allowing them to interfere with driver state.

Exploitation requires triggering DSP responses after stream closure, which can be achieved by a malicious audio application or compromised firmware. An unprivileged local user may be able to cause a race condition by closing a stream while DSP responses are still in flight, no authentication is needed to trigger the bug. The driver operates in kernel space, so a successful trigger results in a lockup.

The impact is a denial of service (DoS) where the audio subsystem becomes unresponsive, potentially affecting system stability. The vulnerability has a CVSS v3 base score of 5.5 (Medium), reflecting the need for local access and the resulting availability impact.

Mitigation is available through Linux kernel stable updates. The fix unconditionally drops all DSP responses associated with closed data streams, preventing the lockup. Administrators should apply the latest kernel patches to protect against this issue. The relevant commits are referenced in [1] and [2].

AI Insight generated on May 18, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

2

News mentions

1