# CVE-2026-72300: ASoC: SOF: topology: validate vendor array size before parsing

> A missing size validation in the Linux kernel SOF topology parser allows out-of-bounds reads via malformed data, potentially causing crashes or information leaks.

- **Severity:** Not scored
- **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:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-72300, DEBIAN-CVE-2026-72300, GHSA-jvfh-wxw8-49hv, UBUNTU-CVE-2026-72300

## What is CVE-2026-72300?

CVE-2026-72300 is a 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: topology: validate vendor array size before parsing

sof_parse_token_sets() reads array->size while iterating over topology
private data. The loop condition only checks that some data remains, so a
malformed topology with a truncated trailing vendor array can make the
parser read the size field before a full vendor-array header is available.

Validate that the remaining private data contains a complete
snd_soc_tplg_vendor_array header before reading array->size.

The declared array size check also needs to remain signed. asize is an int,
but sizeof(*array) has type size_t, so comparing them directly promotes
negative asize values to unsigned and lets them pass the check,
as reported in the stable review thread reference below.

Cast sizeof(*array) to int when validating the declared array size. This
rejects negative, zero and otherwise too-small sizes before the parser
dispatches to the tuple-specific code.

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


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

Apply the vendor's patch.

## Is CVE-2026-72300 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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