# CVE-2026-97930: ALSA: usbusx2y: fix in04_last array size mismatch with in04_buf

> A buffer over-read in the ALSA usbusx2y driver allows local attackers to read out-of-bounds memory or cause a system crash.

- **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:** 25 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-104204, BELL-CVE-2026-97930, DEBIAN-CVE-2026-97930, GHSA-2x7p-4659-c97x, UBUNTU-CVE-2026-97930

## What is CVE-2026-97930?

CVE-2026-97930 is a memory corruption vulnerability in Linux, published on 25 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:

ALSA: usbusx2y: fix in04_last array size mismatch with in04_buf

The in04_last array in struct usx2ydev is declared as char[24], but
in04_buf is allocated as sizeof(struct us428_ctls) which is 21 bytes.
In i_usx2y_in04_int(), when ctl_snapshot_last == -2 (initialization
path):

    memcpy(usx2y->in04_last, usx2y->in04_buf, sizeof(usx2y->in04_last));

This copies 24 bytes from a 21-byte slab allocation, reading 3 bytes
past the end of the source object.

Introduce a USX2Y_IN04_SIZE constant defined as sizeof(struct
us428_ctls) and use it consistently for the in04_last array, the
in04_buf allocation, the URB transfer length, and the comparison loop,
replacing the bare 24 and 21 literals throughout.

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


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

Apply the vendor's patch.

## Is CVE-2026-97930 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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