linux-cve-announce - CVE-2025-71081: ASoC: stm32: sai: fix OF node leak on probe

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2026011338-CVE-2025-71081-df43@gregkh>
Date: Tue, 13 Jan 2026 16:35:40 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-71081: ASoC: stm32: sai: fix OF node leak on probe

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

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

ASoC: stm32: sai: fix OF node leak on probe

The reference taken to the sync provider OF node when probing the
platform device is currently only dropped if the set_sync() callback
fails during DAI probe.

Make sure to drop the reference on platform probe failures (e.g. probe
deferral) and on driver unbind.

This also avoids a potential use-after-free in case the DAI is ever
reprobed without first rebinding the platform driver.

The Linux kernel CVE team has assigned CVE-2025-71081 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 4.15 with commit 5914d285f6b782892a91d6621723fdc41a775b15 and fixed in 6.1.160 with commit acda653169e180b1d860dbb6bc5aceb105858394
	Issue introduced in 4.15 with commit 5914d285f6b782892a91d6621723fdc41a775b15 and fixed in 6.6.120 with commit 4054a3597d047f3fe87864ef87f399b5d523e6c0
	Issue introduced in 4.15 with commit 5914d285f6b782892a91d6621723fdc41a775b15 and fixed in 6.12.64 with commit bae74771fc5d3b2a9cf6f5aa64596083d032c4a3
	Issue introduced in 4.15 with commit 5914d285f6b782892a91d6621723fdc41a775b15 and fixed in 6.18.4 with commit 3752afcc6d80d5525e236e329895ba2cb93bcb26
	Issue introduced in 4.15 with commit 5914d285f6b782892a91d6621723fdc41a775b15 and fixed in 6.19-rc1 with commit 23261f0de09427367e99f39f588e31e2856a690e

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2025-71081
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	sound/soc/stm/stm32_sai.c
	sound/soc/stm/stm32_sai_sub.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/acda653169e180b1d860dbb6bc5aceb105858394
	https://git.kernel.org/stable/c/4054a3597d047f3fe87864ef87f399b5d523e6c0
	https://git.kernel.org/stable/c/bae74771fc5d3b2a9cf6f5aa64596083d032c4a3
	https://git.kernel.org/stable/c/3752afcc6d80d5525e236e329895ba2cb93bcb26
	https://git.kernel.org/stable/c/23261f0de09427367e99f39f588e31e2856a690e