CVE-2026-98940: Linux kernel · ASoC: qcom: lpass-cpu: use DAI table index for playback constraints
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 28 Oct 2026, 02:15 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Exploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in the affected Linux kernel versions listed. Users should update to these patched versions to resolve the incorrect DAI table access issue.
Description
A flaw in the Linux kernel ASoC qcom lpass-cpu driver caused incorrect indexing of the DAI driver table when configuring playback constraints. This could lead to out-of-bounds memory writes on platforms where DAI IDs are sparse, such as IPQ806x. The issue was fixed by using the loop index instead of the DAI ID for indexing the driver table during playback constraint updates.
References
- ubuntu.com/security/CVE-2026-98940 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-98940 (opens in a new tab)
- git.kernel.org/stable/c/6833f1893ac2ec40016c348779af63debf3700d2 (opens in a new tab)
- git.kernel.org/stable/c/69d2b7a4c115181629eb14d800aecc3e7de3f7fb (opens in a new tab)
- git.kernel.org/stable/c/775df6a27e8433e2414124472938009b958f9a77 (opens in a new tab)
- git.kernel.org/stable/c/ca51771c8efde5df05476ac98dd1b2af4e2b149f (opens in a new tab)
- git.kernel.org/stable/c/f11336e6d3cd9e28e5cdf1cb8a6171e7c3eff4e4 (opens in a new tab)