# ALSA: ctxfi: Fix missing SPDIFI1 index handling

CVE record · `CVE-2026-31776`

- **Identifiers:** `CVE-2026-31776`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 1 May 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 1 May 2026, 14:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `a2dbaeb5c61ef110ceefe0d48fe94d428d3bcf16 to before 950decf59d4e978b60a792ce0b3e1555a608f489` (git)
  - affected: `a2dbaeb5c61ef110ceefe0d48fe94d428d3bcf16 to before b045ab3dff97edae6d538eeff900a34c098761f8` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.19`
  - unaffected: `before 6.19` (semver)
  - unaffected: `6.19.12 to 6.19.*, inclusive` (semver)
  - unaffected: `7.0 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel ALSA ctxfi sound driver is affected in version 6.19 before 6.19.12. Missing handling for the SPDIF1 device type on hw20k2 leads to an out-of-bounds array access, and the source gives few details on what an attacker would need. Upgrade to Linux kernel 6.19.12 or later, or to 7.0 or later.

Written 17 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0012, the 1st percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 1 May 2026, 14:15 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-31776)
- 1 May 2026, 15:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-31776)

## Sources

- [CVE List: CVE-2026-31776](https://www.cve.org/CVERecord?id=CVE-2026-31776)
- [NVD: CVE-2026-31776](https://nvd.nist.gov/vuln/detail/CVE-2026-31776)

### References from the CNA

- <https://git.kernel.org/stable/c/950decf59d4e978b60a792ce0b3e1555a608f489>
- <https://git.kernel.org/stable/c/b045ab3dff97edae6d538eeff900a34c098761f8>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-31776>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-31776/>. Everything for agents: <https://agentprime.io/llms.txt>.
