# CVE-2026-98940: ASoC: qcom: lpass-cpu: use DAI table index for playback constraints


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** AZL-110732, BELL-CVE-2026-98940, DEBIAN-CVE-2026-98940, GHSA-h32j-cg7c-ppw6, UBUNTU-CVE-2026-98940

## What is CVE-2026-98940?

CVE-2026-98940 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

ASoC: qcom: lpass-cpu: use DAI table index for playback constraints

The DAI ID is a hardware port ID and is not necessarily the index of
the corresponding entry in variant->dai_driver.

When configuring a DAI with LPAIF_I2SCTL_MODE_QUAD01, the probe code
currently uses dai_id to index variant->dai_driver. This is incorrect
for platforms where DAI IDs are sparse. For example, the IPQ806x MI2S
DAI has ID 4 while it is the only entry in the DAI driver table. If
that DAI is configured for QUAD01 and probe reaches this branch, the
code writes beyond that single entry via dai_driver[4] instead of
updating the DAI being processed.

Use the loop index i when updating the current DAI's playback channel
constraints, while retaining dai_id for indexing the hardware-port
specific playback SD-line mode array.

This fixes the incorrect DAI table access for platforms where the DAI
ID does not match its position in the driver table.

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


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

Upgrade to a fixed version.

## Is CVE-2026-98940 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98940 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-98940 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-98940/ (Markdown: https://insights.sbomify.com/CVE-2026-98940/index.md)
```

## Sources

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

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