CVE-2025-21870
What it is
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
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Weakness
- CWE-476 · NULL pointer dereference
- Record status
- Modified
Affected
- Linux Kernel < 6.12.17
- Linux Kernel < 6.13.5
- Linux Kernel 6.14
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-21870.md and follow it. Check whether this project is affected by CVE-2025-21870. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/6fd60136d256b3b948333ebdb3835f41a95ab7ef
- https://git.kernel.org/stable/c/87c8768a96092ce75cd47fe076db5080db7ac515
- https://git.kernel.org/stable/c/93c6c2e5801aab09ef1ef99f248f3cd323c3f152
References
- https://git.kernel.org/stable/c/6b6b47c1aa717a0ed3400e00a81dfea686a41d7f
- https://git.kernel.org/stable/c/6fd60136d256b3b948333ebdb3835f41a95ab7ef
- https://git.kernel.org/stable/c/87c8768a96092ce75cd47fe076db5080db7ac515
- https://git.kernel.org/stable/c/93c6c2e5801aab09ef1ef99f248f3cd323c3f152
- https://git.kernel.org/stable/c/ec8f5a4fe296c311d4b45db7a25a0e9e69802372