# CVE-2026-72304: ASoC: SOF: ipc4-control: Fix TOCTOU in sof_ipc4_bytes_put

> A time-of-check time-of-use race condition in the Linux kernel's SOF IPC4 control allows attackers to read stale data or corrupt memory via crafted audio control operations.

- **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:** 15 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** BELL-CVE-2026-72304, DEBIAN-CVE-2026-72304, GHSA-p327-qw84-66rm, UBUNTU-CVE-2026-72304

## What is CVE-2026-72304?

CVE-2026-72304 is a high-severity 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: SOF: ipc4-control: Fix TOCTOU in sof_ipc4_bytes_put

In sof_ipc4_bytes_put(), the copy size is derived from the old
data->size in the buffer rather than the incoming new data's size
field from ucontrol. If the new data has a different size, the copy
uses the wrong length: it may truncate valid data or copy stale bytes.

Fix by validating and using the incoming data's sof_abi_hdr.size from
ucontrol before copying.

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


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

Apply the vendor's patch.

## Is CVE-2026-72304 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72304 is a high-severity 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-72304 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-72304/ (Markdown: https://insights.sbomify.com/CVE-2026-72304/index.md)
```

## Sources

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

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