# CVE-2023-54096: soundwire: fix enumeration completion

> A flaw in the Linux kernel soundwire subsystem can lead to memory corruption and denial of service due to improper completion signaling.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2023-54096, DEBIAN-CVE-2023-54096, GHSA-qr7q-qr63-44c5, UBUNTU-CVE-2023-54096

## What is CVE-2023-54096?

CVE-2023-54096 is a high-severity memory corruption vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2023-54096?


## How do I fix CVE-2023-54096?

Apply the vendor's patch.

## Is CVE-2023-54096 being exploited?

There is no known exploitation of CVE-2023-54096 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-54096 and fix it if it is affected.

What it is: CVE-2023-54096 is a high-severity memory corruption vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-54096 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-54096/ (Markdown: https://insights.sbomify.com/CVE-2023-54096/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-54096
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-54096
- OSV: https://osv.dev/vulnerability/CVE-2023-54096

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-54096/
Summaries are generated and may contain mistakes; the official description above is the record.