# CVE-2026-80966: ALSA: portman2x4: Check card index validity at probe

> A missing check in the ALSA portman2x4 driver allows out-of-bounds access, potentially causing crashes or information leaks for local attackers.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-100620, BELL-CVE-2026-80966, DEBIAN-CVE-2026-80966, GHSA-q972-jx45-qf27, UBUNTU-CVE-2026-80966

## What is CVE-2026-80966?

CVE-2026-80966 is a memory corruption vulnerability in Linux, published on 11 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: portman2x4: Check card index validity at probe

Although portman2x4 driver has a check of the given devptr->id value,
it doesn't check for a negative id, which is often given as "none" or
such value when bound via sysfs.  This may lead to OOB access for
index[] and other parameters.

Add a sanity check for the card index and warn/correct it if it's a
value out of the range.

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


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

Apply the vendor's patch.

## Is CVE-2026-80966 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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