CVE-2025-21870: ASoC: SOF: ipc4-topology: Harden loops for looking up ALH copiers
In the Linux kernel, the following vulnerability has been resolved:
ASoC: SOF: ipc4-topology: Harden loops for looking up ALH copiers
Other, non DAI copier widgets could have the same stream name (sname) as
the ALH copier and in that case the copier->data is NULL, no alh_data is
attached, which could lead to NULL pointer dereference.
We could check for this NULL pointer in sof_ipc4_prepare_copier_module()
and avoid the crash, but a similar loop in sof_ipc4_widget_setup_comp_dai()
will miscalculate the ALH device count, causing broken audio.
The correct fix is to harden the matching logic by making sure that the
1. widget is a DAI widget - so dai = w->private is valid
2. the dai (and thus the copier) is ALH copier
Security readout for executives and security teams
Plain-English summary
CVE-2025-21870 is a Linux kernel audio subsystem bug. Under specific Sound Open Firmware topology conditions, the kernel can dereference a missing pointer, potentially causing a crash or broken audio behavior. The sources do not provide CVSS, remote attackability, privilege requirements, or evidence of exploitation.
Executive priority
Treat this as a routine kernel maintenance issue unless affected Linux audio paths are business-critical. The available evidence supports operational reliability concern, but not emergency response or active exploitation handling.
Technical view
The issue affects ASoC SOF ipc4-topology ALH copier lookup logic. Matching only by stream name can select a non-DAI copier widget whose data is NULL. The fix hardens matching so the widget is DAI-backed and the copier is actually an ALH copier.
Likely exposure
Exposure appears limited to Linux systems using the affected SOF IPC4 audio topology paths. The source bundle lists Linux kernel versions including 6.0, 6.12.17, 6.13.5, and 6.14 as affected, but does not define distribution package status.
Exploitation context
No active exploitation is indicated. The CVE is not marked KEV, and the provided sources describe a reliability flaw leading to NULL pointer dereference or broken audio, not a public exploit path.
Researcher notes
The record lacks CVSS, CWE, attack vector, and privilege details. Analysis should stay close to the kernel commit rationale: ambiguous stream-name matching can select the wrong widget type, leaving copier data absent and causing NULL dereference or ALH count errors.
Mitigation direction
Apply vendor kernel updates containing the referenced stable fixes.
Check Linux distribution advisories for package-specific fixed versions.
Prioritize systems using SOF IPC4 audio hardware or ALH copier paths.
If patching is delayed, monitor for kernel audio crashes and instability.
Validation and detection
Inventory Linux kernel versions across affected endpoints and appliances.
Check whether deployed kernels include the referenced stable commits.
Review distribution security trackers for CVE-2025-21870 package status.
Confirm affected systems use SOF IPC4 audio topology paths where relevant.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-21870 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
4Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Mar 27, 2025, 13:38 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.