[CVE-2026-80525][LOW] ASoC: SOF: ipc4-topology: Refresh copier IPC payload before widget setup

[CVE-2026-80525][LOW] ASoC: SOF: ipc4-topology: Refresh copier IPC payload before widget setup

[AL-KERNEL]

CVE: CVE-2026-80525
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: ASoC: SOF: ipc4-topology: Refresh copier IPC payload before widget setup
Commit: decb87e76716d11d846c9c055e309c8ff90d7656
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=decb87e76716d11d846c9c055e309c8ff90d7656
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80525
Analysis date: Wed, 26 Aug 2026 11:47:45 -0400
ActionableScore: 2
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate / Low-like, auto-close candidate
Manual review required: NO

Summary:
No one-sentence report phrase was found.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-80525 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80525

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: LOW
Manual review required: NO

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-80525	LOW	CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H';CWE-665;*CWE-664;CWE-754;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.5';DESCR 'ASoC SOF IPC4 copier widgets can reuse a stale ipc_config_data payload after suspend and resume because the widget list persists and ipc_prepare is not run again. The cached payload may contain boot-time host or link DMA stream tags while the underlying copier data and dma_config_tlv have already been updated with newly allocated DMA identifiers. On affected Intel SOF systems this can send inconsistent DMA channel assignments to firmware and can trigger DMA channel conflicts, firmware errors, or firmware crashes. For the CVSS the PR:L is used because a local user or local audio process may be able to exercise PCM setup and runtime resume paths, but reliable triggering depends on platform power management and audio routing. The issue is not network reachable. Impact is denial of service to the audio firmware or audio subsystem, with no evidence of kernel memory corruption, information disclosure, or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like, auto-close candidate (with actual score 2)	YES	DANGER DMAorINTERRUPT HARDWARE MEMORY  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	YES	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=2

1. ActionableScore
* Conservative score: 2
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate / Low-like, auto-close candidate**::

2. Signal breakdown
* Local unprivileged trigger: +1. A local user or local audio process may exercise PCM setup and suspend/resume related audio paths on affected Intel SOF IPC4 systems.
* Availability impact realistic: +1. The stale IPC payload can cause DMA channel conflicts and SOF firmware errors or crashes, affecting audio availability.
* No memory corruption signal: +0. The patch refreshes stale cached configuration data before sending IPC to firmware. It does not show UAF, OOB access, double free, type confusion, arbitrary write, or kernel object lifetime corruption.
* No network reachability: +0. The affected path is local audio firmware setup, not a remote protocol or packet-processing path.
* No privilege escalation plausibility: +0. The described consequence is firmware error or firmware crash, not kernel memory control or security-boundary bypass.
* Platform and sequence dependence: effectively limiting. Triggering depends on affected Intel SOF IPC4 hardware, suspend/resume, DMA stream reallocation, and audio topology behavior.

3. Reachability analysis
A local user may plausibly trigger the relevant path by using audio streams across suspend/resume on an affected Intel SOF IPC4 platform. No remote attacker can directly reach this code path. Namespace or container behavior does not materially lower the privilege requirement unless the container is explicitly given access to host audio devices and power-management behavior. The subsystem is common on some Intel audio platforms, but the exact bug depends on SOF IPC4 copier widgets and stale DMA identifiers after suspend/resume.

4. Severity interpretation
This behaves like an ordinary Moderate or Low-like device-specific DoS issue. The realistic impact is loss or crash of the audio firmware or audio subsystem. There is no supported evidence of kernel memory corruption, information disclosure, privilege escalation, or cross-boundary policy bypass. The theoretical risk should not be upgraded beyond availability because the stale data is a DMA configuration payload sent to firmware, not an attacker-controlled kernel overwrite primitive.

5. One-sentence report phrase
ASoC SOF IPC4 copier widgets may reuse stale cached DMA identifiers after suspend and resume, causing DMA channel conflicts and SOF firmware crashes on affected Intel audio platforms.

6. Manual review recommendation
NO MANUAL CHECK NEEDED. The patch and commit context indicate a local, platform-specific stale configuration bug with firmware/audio DoS impact only, and no concrete memory corruption or privilege escalation primitive.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: ASoC: SOF: ipc4-topology: Refresh copier IPC payload before widget setup
Commit: decb87e76716d11d846c9c055e309c8ff90d7656
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=decb87e76716d11d846c9c055e309c8ff90d7656

Commit description:

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.

Fixes: e9c6b11 ("ASoC: SOF: make dma_config_tlv be an array")
Cc: stable@vger.kernel.org
Link: thesofproject/sof#10700
Link: thesofproject/sof#10955
Signed-off-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
Reviewed-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Reviewed-by: Liam Girdwood <liam.r.girdwood@intel.com>
Link: https://patch.msgid.link/20260730054822.5913-1-peter.ujfalusi@linux.intel.com
Signed-off-by: Mark Brown <broonie@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  sound/soc/sof/ipc4-topology.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=decb87e76716d11d846c9c055e309c8ff90d7656

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-80525 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80525

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
  The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 5.5

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: unknown
  Paranoid ActionableScore: 2

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).