# CVE-2026-93280: greybus: audio: bound the topology section sizes against the fetched size

> A malicious Greybus module can trigger out-of-bounds reads in the Linux kernel audio driver by providing inconsistent topology section sizes.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/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:** 24 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-93280, DEBIAN-CVE-2026-93280, GHSA-mwmc-pxhm-4fx8, UBUNTU-CVE-2026-93280

## What is CVE-2026-93280?

CVE-2026-93280 is a high-severity memory corruption vulnerability in Linux, published on 24 Sep 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:

greybus: audio: bound the topology section sizes against the fetched size

gb_audio_gb_get_topology() fetches a topology blob of a module-supplied
size, and gbaudio_tplg_parse_data() then walks it by adding the
module-supplied size_dais, size_controls and size_widgets fields to
form the control, widget and route section offsets. Those le32 sizes
are never checked against the fetched blob, so a module reporting a
small topology size but large section sizes makes the offsets point
past the allocation, and parsing reads out of bounds.

Reject a topology whose section sizes do not fit within the fetched
size before it is parsed.

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


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

Apply the vendor's patch.

## Is CVE-2026-93280 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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