# CVE-2026-72301: ASoC: SOF: ipc3-control: Fix TOCTOU in bytes_put and bytes_get

> A time-of-check to time-of-use race condition in the Linux kernel's SOF IPC3 control allows attackers to read or modify memory via incorrect size validation in bytes_put and bytes_get.

- **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-72301, DEBIAN-CVE-2026-72301, GHSA-m237-j8mr-f2gj, UBUNTU-CVE-2026-72301

## What is CVE-2026-72301?

CVE-2026-72301 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: ipc3-control: Fix TOCTOU in bytes_put and bytes_get

In sof_ipc3_bytes_put(), the size used for the memcpy is derived from
the old data->size already in the buffer, not the incoming new data's
size field. If the new data has a different size, the copy length is
wrong: it may truncate valid data or copy stale bytes.

Similarly, sof_ipc3_bytes_get() checks data->size against max_size
without accounting for the sizeof(struct sof_ipc_ctrl_data) offset
of the flex array within the allocation.

Fix bytes_put to validate and use the incoming data's sof_abi_hdr.size
from ucontrol before copying. Fix bytes_get to subtract sizeof(*cdata)
from the bounds check to match the actual available space.

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


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

Apply the vendor's patch.

## Is CVE-2026-72301 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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