# CVE-2026-74332: ASoC: amd: acp-sdw-sof: Bound DAI link iteration

> An out-of-bounds read in the AMD ACP SoundWire driver can cause a kernel crash or leak memory when all DAI entries are initialized.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** BELL-CVE-2026-74332, DEBIAN-CVE-2026-74332, GHSA-vwrj-mgjx-j4g8, UBUNTU-CVE-2026-74332

## What is CVE-2026-74332?

CVE-2026-74332 is a high-severity memory corruption vulnerability in Linux, published on 15 Aug 2026. 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:

ASoC: amd: acp-sdw-sof: Bound DAI link iteration

create_sdw_dailinks() walks sof_dais until it finds an entry with
initialised cleared, but sof_dais is allocated with exactly num_ends
entries. If all entries are initialised, the loop reads past the end of
the array.

Pass the allocated entry count to create_sdw_dailinks() and stop before
reading past the array.

## Which versions are affected by CVE-2026-74332?


## How do I fix CVE-2026-74332?

Apply the vendor's patch.

## Is CVE-2026-74332 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74332 and fix it if it is affected.

What it is: CVE-2026-74332 is a high-severity memory corruption vulnerability in Linux, published on 15 Aug 2026. 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-2026-74332 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-2026-74332/ (Markdown: https://insights.sbomify.com/CVE-2026-74332/index.md)
```

## Sources

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

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