CVE-2026-98940ASoC: qcom: lpass-cpu: use DAI table index for playback constraints
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 28 days later
· 28 days later
Published
- 7 days later
· 7 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (14 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected c223f41c1a52bfe10f1d3311679b1d1f9813e500 – < c10823507a74d7474391c01121e3f59901b1789f
- affected c223f41c1a52bfe10f1d3311679b1d1f9813e500 – < 63987bb73df65fb01245b5905b005aa47c1dd27a
- affected c223f41c1a52bfe10f1d3311679b1d1f9813e500 – < 775df6a27e8433e2414124472938009b958f9a77
- affected c223f41c1a52bfe10f1d3311679b1d1f9813e500 – < 6833f1893ac2ec40016c348779af63debf3700d2
- affected c223f41c1a52bfe10f1d3311679b1d1f9813e500 – < 69d2b7a4c115181629eb14d800aecc3e7de3f7fb
- affected c223f41c1a52bfe10f1d3311679b1d1f9813e500 – < f11336e6d3cd9e28e5cdf1cb8a6171e7c3eff4e4
- affected c223f41c1a52bfe10f1d3311679b1d1f9813e500 – < ca51771c8efde5df05476ac98dd1b2af4e2b149f
- affected 5.14
- unaffected < 5.14
- unaffected 5.15.224 – ≤ 5.15.*
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.113 – ≤ 6.12.*
- unaffected 6.18.56 – ≤ 6.18.*
- unaffected 7.2.10 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References7
- https://git.kernel.org/stable/c/c10823507a74d7474391c01121e3f59901b1789f (opens in a new tab)
- https://git.kernel.org/stable/c/63987bb73df65fb01245b5905b005aa47c1dd27a (opens in a new tab)
- https://git.kernel.org/stable/c/775df6a27e8433e2414124472938009b958f9a77 (opens in a new tab)
- https://git.kernel.org/stable/c/6833f1893ac2ec40016c348779af63debf3700d2 (opens in a new tab)
- https://git.kernel.org/stable/c/69d2b7a4c115181629eb14d800aecc3e7de3f7fb (opens in a new tab)
- https://git.kernel.org/stable/c/f11336e6d3cd9e28e5cdf1cb8a6171e7c3eff4e4 (opens in a new tab)
- https://git.kernel.org/stable/c/ca51771c8efde5df05476ac98dd1b2af4e2b149f (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-108912 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98940)Record last updated .