# CVE-2026-72302: ASoC: SOF: ipc3-control: Use overflow checks in control_update size calc

> An integer overflow in the Linux kernel's SOF IPC3 control update allows out-of-bounds access, potentially leading to code execution or denial of service.

- **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-72302, DEBIAN-CVE-2026-72302, GHSA-vwf3-ww8v-29c4, UBUNTU-CVE-2026-72302

## What is CVE-2026-72302?

CVE-2026-72302 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: Use overflow checks in control_update size calc

In sof_ipc3_control_update(), the expected_size calculation uses
firmware-provided cdata->num_elems in arithmetic that could overflow
on 32-bit platforms, wrapping to a small value. This would allow the
cdata->rhdr.hdr.size comparison to pass with mismatched sizes,
potentially leading to out-of-bounds access in snd_sof_update_control.

Use check_mul_overflow() and check_add_overflow() to detect and reject
overflowed size calculations.

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


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

Apply the vendor's patch.

## Is CVE-2026-72302 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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