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

ASoC: SOF: ipc4-topology: Refresh copier IPC payload before widget setup

The ipc_config_data buffer for copier widgets is built once during
ipc_prepare (called from sof_pcm_setup_connected_widgets) and cached
for reuse. For host copiers this buffer contains the copier_data with
gtw_cfg.node_id (host DMA ID). For DAI copiers it additionally includes
a dma_config_tlv trailer with stream_id and dma_channel_id for HDA link
DMA.

On suspend/resume, both host and link DMA streams are released and
re-allocated with potentially different stream tags. The underlying
copier_data and dma_config_tlv structures are correctly updated by
host_config and sdw_hda_dai_hw_params respectively. However, since the
widget list (spcm->stream[].list) persists across suspend,
sof_pcm_hw_params skips sof_pcm_setup_connected_widgets and ipc_prepare
never runs again to rebuild ipc_config_data. The stale cached payload
is then sent to firmware with boot-time DMA channel assignments, causing
DMA channel conflicts that lead to firmware errors and crashes.

Fix this by refreshing copier_data and dma_config_tlv portions of
ipc_config_data in sof_ipc4_widget_setup right before the IPC message
is sent. This ensures the payload always reflects the current DMA state
regardless of whether ipc_prepare ran.

For DAI copiers, the gtw_cfg.config_length in copier_data is temporarily
inflated to include the TLV size (matching the ipc_config_data layout)
before copying, then restored, mirroring what
sof_ipc4_prepare_copier_module does when first building the buffer.
Published: 2026-08-26
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

In the Linux kernel’s ALSA System on Chip (ASoC) subsystem, a cached IPC payload for copier widgets is reused across suspend and resume cycles. The payload contains DMA channel identifiers that may change when the system resumes, but the code fails to rebuild the buffer, causing the firmware to receive stale DMA assignments. This mismatch leads to DMA channel conflicts that manifest as firmware errors and crashes, interrupting audio functionality.

Affected Systems

Vulnerability affects the Linux kernel’s audio subsystem (ASoC) in all distributions that include the captured code path, particularly versions that have not yet incorporated the patch described in the referenced git commits. The issue is present in the ASoC SOF (Sound Open Firmware) components handling the ipc4 topology. No specific vendor or product name beyond the generic Linux kernel is listed, so any system running that kernel component is potentially affected.

Risk and Exploitability

If an attacker can control or influence audio suspend/resume sequences (for example, via user space audio applications or the kernel’s audio driver), they can trigger the flawed IPC payload usage. The exploit would lead to firmware crashes rather than arbitrary code execution, constituting a denial‑of‑service risk that could affect embedded systems or machines with critical audio services. The CVSS score is not supplied, and EPSS is unavailable; the vulnerability is not in the CISA KEV catalog, implying limited public exploitation yet. The likely attack vector is local, requiring privileged access to audio drivers or the ability to execute user space code that interacts with the ASO audio interfaces.

Generated by OpenCVE AI on August 26, 2026 at 15:45 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that includes the fix for the ASoC SOF ipc4 topology bug.
  • Reboot the system so the updated kernel and firmware are loaded.
  • Until a kernel update is available, avoid suspend–resume cycles for audio devices or disable the audio subsystem to reduce the risk of firmware crashes.

Generated by OpenCVE AI on August 26, 2026 at 15:45 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 26 Aug 2026 16:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-665

Wed, 26 Aug 2026 14:45:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: ipc4-topology: Refresh copier IPC payload before widget setup The ipc_config_data buffer for copier widgets is built once during ipc_prepare (called from sof_pcm_setup_connected_widgets) and cached for reuse. For host copiers this buffer contains the copier_data with gtw_cfg.node_id (host DMA ID). For DAI copiers it additionally includes a dma_config_tlv trailer with stream_id and dma_channel_id for HDA link DMA. On suspend/resume, both host and link DMA streams are released and re-allocated with potentially different stream tags. The underlying copier_data and dma_config_tlv structures are correctly updated by host_config and sdw_hda_dai_hw_params respectively. However, since the widget list (spcm->stream[].list) persists across suspend, sof_pcm_hw_params skips sof_pcm_setup_connected_widgets and ipc_prepare never runs again to rebuild ipc_config_data. The stale cached payload is then sent to firmware with boot-time DMA channel assignments, causing DMA channel conflicts that lead to firmware errors and crashes. Fix this by refreshing copier_data and dma_config_tlv portions of ipc_config_data in sof_ipc4_widget_setup right before the IPC message is sent. This ensures the payload always reflects the current DMA state regardless of whether ipc_prepare ran. For DAI copiers, the gtw_cfg.config_length in copier_data is temporarily inflated to include the TLV size (matching the ipc_config_data layout) before copying, then restored, mirroring what sof_ipc4_prepare_copier_module does when first building the buffer.
Title ASoC: SOF: ipc4-topology: Refresh copier IPC payload before widget setup
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-26T14:37:04.973Z

Reserved: 2026-08-26T14:34:25.764Z

Link: CVE-2026-80525

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-26T15:17:06.200

Modified: 2026-08-26T15:17:06.200

Link: CVE-2026-80525

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-26T18:15:08Z

Weaknesses