linux-cve-announce - CVE-2023-54096: soundwire: fix enumeration completion

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: <2025122408-CVE-2023-54096-efde@gregkh>
Date: Wed, 24 Dec 2025 14:06:53 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-54096: soundwire: fix enumeration completion

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

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

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

soundwire: fix enumeration completion

The soundwire subsystem uses two completion structures that allow
drivers to wait for soundwire device to become enumerated on the bus and
initialised by their drivers, respectively.

The code implementing the signalling is currently broken as it does not
signal all current and future waiters and also uses the wrong
reinitialisation function, which can potentially lead to memory
corruption if there are still waiters on the queue.

Not signalling future waiters specifically breaks sound card probe
deferrals as codec drivers can not tell that the soundwire device is
already attached when being reprobed. Some codec runtime PM
implementations suffer from similar problems as waiting for enumeration
during resume can also timeout despite the device already having been
enumerated.

The Linux kernel CVE team has assigned CVE-2023-54096 to this issue.


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

	Issue introduced in 5.7 with commit fb9469e54fa7a7b6a8137c40ae66c41b8d0ab175 and fixed in 5.10.190 with commit 48d1d0ce0782f995fda678508fdae35c5e9593f0
	Issue introduced in 5.7 with commit fb9469e54fa7a7b6a8137c40ae66c41b8d0ab175 and fixed in 5.15.126 with commit a36b522767f3a72688893a472e80c9aa03e67eda
	Issue introduced in 5.7 with commit fb9469e54fa7a7b6a8137c40ae66c41b8d0ab175 and fixed in 6.1.43 with commit e1d54962a63b6ec04ed0204a3ecca942fde3a6fe
	Issue introduced in 5.7 with commit fb9469e54fa7a7b6a8137c40ae66c41b8d0ab175 and fixed in 6.4.8 with commit c5265691cd065464d795de5666dcfb89c26b9bc1
	Issue introduced in 5.7 with commit fb9469e54fa7a7b6a8137c40ae66c41b8d0ab175 and fixed in 6.5 with commit c40d6b3249b11d60e09d81530588f56233d9aa44

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-2023-54096
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:
	drivers/soundwire/bus.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/48d1d0ce0782f995fda678508fdae35c5e9593f0
	https://git.kernel.org/stable/c/a36b522767f3a72688893a472e80c9aa03e67eda
	https://git.kernel.org/stable/c/e1d54962a63b6ec04ed0204a3ecca942fde3a6fe
	https://git.kernel.org/stable/c/c5265691cd065464d795de5666dcfb89c26b9bc1
	https://git.kernel.org/stable/c/c40d6b3249b11d60e09d81530588f56233d9aa44